Skip to main content
Glama

get_ifc_quantities

Extract and retrieve basic quantity takeoff data from IFC building models for project analysis and reporting.

Instructions

Extract and get basic qtos about the IFC project.

Returns:
    A JSON-formatted string with project quantities information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_ifc_quantities' MCP tool. It connects to the Blender addon via socket and sends a 'get_ifc_quantities' command, returning the JSON-formatted quantities data or error message.
    def get_ifc_quantities() -> str:
        """
        Extract and get basic qtos about the IFC project.
        
        Returns:
            A JSON-formatted string with project quantities information
        """
        try:
            blender = get_blender_connection()
            result = blender.send_command("get_ifc_quantities")
            
            # Return the formatted JSON of the results
            return json.dumps(result, indent=2)
        except Exception as e:
            logger.error(f"Error getting IFC project quantities: {str(e)}")
            return f"Error getting IFC project quantities: {str(e)}"
  • tools.py:614-614 (registration)
    The @mcp.tool() decorator registers the 'get_ifc_quantities' function as an MCP tool.
    def get_ifc_quantities() -> str:
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the return format ('JSON-formatted string') but doesn't disclose behavioral traits like whether this is a read-only operation, potential performance impacts, or any prerequisites. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 brief and front-loaded with the core purpose in the first sentence. The second sentence about return format is useful but could be integrated more smoothly. Overall, it's efficient with minimal waste, though slightly fragmented.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete. It doesn't explain what 'basic qtos' includes, how the data is structured, or any limitations. For a data retrieval tool in a context with many similar siblings, more detail is needed to ensure proper use.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds no parameter information, which is appropriate here. Baseline is 4 for zero parameters, as no compensation is needed.

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

Purpose3/5

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

The description states the tool 'Extract and get basic qtos about the IFC project' which provides a general purpose (extract quantities) but lacks specificity. It doesn't clearly distinguish from siblings like 'get_ifc_project_info' or 'get_ifc_properties', making it somewhat vague about what exactly 'qtos' (quantities) entails compared to other data retrieval tools.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get_ifc_project_info' and 'get_ifc_properties' that might retrieve overlapping or related data, the description offers no context about when this specific quantity extraction is appropriate, leaving usage decisions unclear.

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/JotaDeRodriguez/Bonsai_mcp'

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