Export only selected objects from Blender to a file. Specify the target filepath and optional format for the export.
Export only selected objects to a file.
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | ||
| filepath | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0+hardened.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only states the action and destination; it does not disclose file-overwrite behavior, default format handling, errors on empty selection, or whether the operation mutates the scene. For an export tool this is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence with zero waste. It is efficient, though it borders on under-specification; but for a simple tool the brevity is acceptable and earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having an output schema (not shown) and a clear sibling contrast, the description is incomplete. It lacks essential operational details such as file overwrite policy, format handling, and behavior with no selection, which an agent would need to call it correctly without trial and error.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It mentions 'to a file' (implying filepath) but gives no explanation of the 'format' parameter, its default, or allowed values. The description adds no meaningful parameter semantics beyond the schema itself.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb (Export), resource (only selected objects), and destination (to a file). It clearly differentiates from the sibling 'export_file' by scoping to selected objects, leaving no ambiguity about what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'only selected objects' implicitly guides the agent to use this when there is a selection and to use export_file otherwise. However, it does not explicitly name the alternative or provide a when-not-to-use condition, so it falls just short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.