bonsai-mcp

Overview Schema Source Related Servers Discussions Admin

ifc_edit_profile

Adjust an element's profile parameters, with safeguards against unintentionally affecting shared geometry unless apply_to_all is set.

Instructions

Change the parameters of an element's parameterised profile.

Refused when the geometry is shared — through an IfcRepresentationMap or a reused profile entity — because the change would silently apply to every element sharing it. The refusal reports how many. Pass apply_to_all=true only when changing all of them is what you actually want.

Refused outright on tessellated geometry: there are no parameters left, and nothing here will tessellate to work around that.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "guid": "<guid>",
      "params": "<params>"
    },
    "name": "ifc_edit_profile"
  }
}

Input Schema

Name	Required	Description	Default
`guid`	Yes
`params`	Yes
`apply_to_all`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations present, the description carries the behavioral disclosure burden. It discloses the non-obvious risk of silent changes to all elements sharing a profile, explains that the refusal reports the count, and states that tessellated geometry is refused outright with no tessellation workaround. This is strong, though it does not mention success-side effects like persistence or undo.

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

Conciseness5/5

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

The description is compact, front-loaded with the core operation, and each of the three short paragraphs earns its place: purpose, shared-geometry refusal, and tessellated-geometry refusal. There is no redundant or filler content.

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

Completeness3/5

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

The description covers scope and refusal behavior well, but it leaves a critical gap around how to supply parameters in the params object, and it does not clarify persistence or reversibility. Output schema exists, so return-value detail is not required, but the missing param guidance prevents the description from being fully complete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description had to compensate for the three parameters. It explains apply_to_all semantically and warns about shared profiles, but the central 'params' object remains undefined: no valid keys, value types, or example are given. An agent would struggle to construct the primary payload correctly.

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

Purpose4/5

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

The opening sentence states a specific verb and resource: 'Change the parameters of an element's parameterised profile.' This clearly distinguishes it from sibling tools that edit attributes, psets, or placements. It stops short of a 5 because it does not explicitly name or contrast with any sibling tool.

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 gives clear usage context: it refuses on shared geometry and tessellated geometry, and it explicitly tells the caller to pass apply_to_all=true only when changing all sharing elements is intended. It lacks explicit alternative-tool routing for those refusal cases, but the when-not conditions are unambiguous.

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