Skip to main content
Glama
shuji-bonji

@shuji-bonji/ifc-core-mcp

Get IFC PropertySet Definition

ifc_get_propertyset
Read-onlyIdempotent

Retrieve full IFC4.3 PropertySet definitions by name or search by keyword. Get property names, data types, and IFC type mappings.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoMode: 'get' for exact name lookup, 'search' for keyword searchget
nameYesPropertySet name (e.g. 'Pset_WallCommon') or search keyword (e.g. 'Wall', 'thermal')
limitNoMaximum results to return
offsetNoNumber of results to skip for pagination
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds value by explaining the dual-mode behavior, pagination, and return structure, though it could detail more about edge cases.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized with clear sections (summary, args, returns, examples) and front-loaded with the purpose. It is slightly verbose by duplicating schema info, but remains readable and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema, the description adequately explains return values and structure. It covers all parameters, modes, and pagination, making it suitable for effective tool use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description repeats schema definitions and adds examples, which clarify usage but do not introduce new semantic meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves or searches IFC PropertySet definitions, specifying the two modes and providing examples. It distinguishes itself from sibling tools like ifc_get_entity and ifc_search_entity by focusing on PropertySets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use 'get' vs 'search' with explicit examples, and the schema enforces mode choices. It does not explicitly contrast with siblings, but the tool's purpose is clear enough for appropriate selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shuji-bonji/ifc-core-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server