Loading ToolBench

Reading the current corpus…

ifc-core-mcp MCP server · C · ToolBench

ifc-core-mcp

MCP server for IFC4.3 specification reference - search and retrieve IFC entity definitions, attributes, inheritance, and PropertySets

2026-07-28+STDIO4 tools

64/100

Definition Quality90

Protocol Readiness45

Supportability33

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

Four well-defined tools with consistent naming patterns (all prefixed with 'ifc_'), comprehensive parameter schemas using JSON Schema with types and descriptions, and clear tool descriptions. All tools are READ_ONLY with no destructive operations. Parameters include proper constraints (enums, min/max, length limits). Descriptions are 150-200+ characters, well above the 10-char minimum. Output schemas are implicitly documented through response_format parameters (markdown/json). However, no explicit output schema documentation in visible code, and no tool annotations (readOnlyHint, etc.) visible in registration. Error handling not explicitly documented in source. All tools follow single-responsibility principle focused on IFC specification reference queries.

Tools (4)

ifc_get_entityread onlysource verified91/100

Get the complete definition of an IFC4.3 entity including attributes, inheritance, WHERE rules, and description. Returns the entity's structural definition from the EXPRESS schema merged with the Markdown documentation.

ifc_get_inheritanceread onlysource verified91/100

Get the inheritance hierarchy of an IFC4.3 entity. Shows ancestor chain (supertypes up to IfcRoot) and/or descendant tree (subtypes).

ifc_get_propertysetread onlysource verified87/100

Get or search IFC4.3 PropertySet definitions. In 'get' mode, retrieves the full definition of a named PropertySet including individual property names, data types, and IFC type mappings. In 'search' mode, searches PropertySets by keyword.

ifc_search_entityread onlysource verified91/100

Search IFC4.3 entities by name or description keyword. Returns matching entities with their name, layer, schema, and short definition. Supports partial name matching and description text search.

Issues (4)

MEDIUMtool-annotations ↗

Tool annotations (readOnlyHint, destructiveHint, idempotentHint) not visible in source code. Tools are READ_ONLY but hint not explicitly declared in registration.

ifc_search_entityifc_get_entityifc_get_inheritanceifc_get_propertyset

MEDIUMresponse-shaper ↗

Output schemas not explicitly documented in visible source. While response_format parameter indicates markdown/json output, the actual schema structure (which fields, types, required) is not visible in parameter definitions or tool documentation.

ifc_search_entityifc_get_entityifc_get_inheritanceifc_get_propertyset

MEDIUMrecovery-guide ↗

Error handling and recovery guidance not documented in tool descriptions. Users/LLMs don't know what to do if a query returns no results, or what 'cannot answer' means vs. true non-existence.

ifc_search_entityifc_get_entityifc_get_inheritanceifc_get_propertyset

Recommendations

Add readOnlyHint: true annotation when registering each tool to explicitly signal that these are read-only reference queries with no side effects. This enables clients to optimize caching and retry policies.
Document explicit output schemas for each tool. Example for ifc_search_entity: { type: 'object', properties: { entities: { type: 'array', items: { type: 'object', properties: { name, layer, schema, definition } } }, total_count: { type: 'number' }, next_offset: { type: 'number' } } }
Enhance tool descriptions to include recovery guidance. Example: 'If no results are found, the entity may not exist in IFC4.3, or try a shorter/different keyword. Call with response_format="json" to see structured data.'
Consider splitting ifc_get_propertyset into two separate tools: ifc_get_propertyset (exact name lookup only) and ifc_search_propertyset (keyword search only). This eliminates mode parameter ambiguity and follows single-responsibility principle.
Add parameter descriptions clarifying what 'no results' means semantically. Document that search results are filtered to IFC4.3 specification data only, and absence of a result does NOT guarantee the entity doesn't exist elsewhere.
Document pagination behavior explicitly: 'Results are limited to avoid context overflow. Use limit and offset for pagination. Total count is returned to enable page calculation.'
Add examples of typical response structures for each output format (markdown vs json) to help LLMs understand what to expect.

Score history

Overall score trend

First recorded score · v2 rubric

64/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	C	64	2026-07-28+	v2