@shuji-bonji/ifc-core-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ifc_search_entityA | 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. Args:
Returns: List of matching entities with name, layer, schema, and short definition. Examples:
|
| ifc_get_entityA | 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. Args:
Returns: Entity definition with attributes, types, inheritance chain, WHERE rules, and description. Examples:
|
| ifc_get_inheritanceA | Get the inheritance hierarchy of an IFC4.3 entity. Shows ancestor chain (supertypes up to IfcRoot) and/or descendant tree (subtypes). Args:
Returns: Inheritance hierarchy showing ancestors and/or descendants. Examples:
|
| ifc_get_propertysetA | 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. Args:
Returns: PropertySet definition with properties (name, dataType, ifcType, valueKind) and descriptions. Examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a distinct purpose: entity definition lookup, inheritance hierarchy, propertyset retrieval/search, and entity search. No functional overlap, clear boundaries.
All tools follow the pattern 'ifc_<verb>_<noun>', but verbs are not perfectly uniform ('get' for three, 'search' for one). Consistent prefix and noun naming, minor verb inconsistency.
Four tools is reasonable for a core IFC schema server. Covers essential lookups without being too sparse or bloated. Could include a few more (e.g., types, quantities) but current count is appropriate.
Covers key aspects of IFC schema: entity definitions, inheritance, propertysets, and search. Missing metadata like types list or quantity sets, but core read operations are well-covered.