Skip to main content
Glama
shuji-bonji

@shuji-bonji/ifc-core-mcp

by shuji-bonji

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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:

  • query (string): Search keyword (e.g. "Wall", "beam", "spatial", "opening")

  • limit (number): Max results, 1-100 (default: 20)

  • offset (number): Pagination offset (default: 0)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: List of matching entities with name, layer, schema, and short definition.

Examples:

  • "Wall" → IfcWall, IfcWallType, IfcWallStandardCase, ...

  • "spatial" → IfcSpatialElement, IfcSpatialStructureElement, ...

  • "beam" → IfcBeam, IfcBeamType, IfcBeamStandardCase, ...

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:

  • name (string): IFC entity name (e.g. "IfcWall", "IfcBeam", "IfcProject")

  • include_inherited (boolean): Include attributes inherited from supertypes (default: true)

  • include_inverse (boolean): Include inverse relationship attributes (default: false)

  • include_description (boolean): Include Markdown description text (default: true)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Entity definition with attributes, types, inheritance chain, WHERE rules, and description.

Examples:

  • "IfcWall" → Wall entity with PredefinedType, supertype chain to IfcRoot

  • "IfcProject" → Project entity with global context attributes

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:

  • name (string): IFC entity name (e.g. "IfcRoot", "IfcProduct", "IfcWall")

  • direction ('descendants' | 'ancestors' | 'both'): Which direction to show (default: 'both')

  • depth (number): Max depth for descendant tree, 1-10 (default: 3)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Inheritance hierarchy showing ancestors and/or descendants.

Examples:

  • "IfcRoot" with direction="descendants" → full class hierarchy tree

  • "IfcWall" with direction="ancestors" → IfcWall → IfcBuiltElement → ... → IfcRoot

  • "IfcProduct" with direction="both" → both ancestor chain and subtype tree

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:

  • name (string): PropertySet name (e.g. "Pset_WallCommon") or search keyword

  • mode ('get' | 'search'): Lookup mode (default: 'get')

  • limit (number): Max results for search mode (default: 20)

  • offset (number): Pagination offset for search mode (default: 0)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: PropertySet definition with properties (name, dataType, ifcType, valueKind) and descriptions.

Examples:

  • name="Pset_WallCommon", mode="get" → Full PropertySet definition with 10 properties

  • name="Wall", mode="search" → All PropertySets related to walls

  • name="thermal", mode="search" → PropertySets with thermal properties

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool serves a distinct purpose: entity definition lookup, inheritance hierarchy, propertyset retrieval/search, and entity search. No functional overlap, clear boundaries.

Naming Consistency4/5

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.

Tool Count4/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues