Retrieve detailed information about a Blender object, including its type, transforms, modifiers, materials, parent, and collections, to support scene inspection and automation.
Get detailed info about an object: type, transforms, modifiers, materials, parent, collections.
| Name | Required | Description | Default |
|---|---|---|---|
| name | 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?
The annotation readOnlyHint=true already declares this is a read-only operation. The description adds no further behavioral details such as error handling, return format, or performance characteristics. Since annotations cover the read-only nature, the description's contribution is minimal.
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?
The description is a single, concise sentence that front-loads the primary action and enumerates the key information types. No redundant words or unnecessary details.
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?
Given that an output schema exists, the description's enumeration of included attributes (type, transforms, modifiers, materials, parent, collections) provides sufficient context. It does not mention error behavior, but for a simple read-only getter with an output schema, this is acceptable.
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?
The schema defines a single 'name' parameter with no description (0% coverage). The description does not elaborate on the parameter's meaning, format, or constraints beyond implying it is the object's name. It fails to compensate for the missing schema documentation.
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 clear verb 'Get' and resource 'detailed info about an object', and lists specific attributes (type, transforms, modifiers, materials, parent, collections). This clearly distinguishes it from more specialized getters like get_mesh_info or get_armature_info, making its purpose unambiguous.
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 description provides no guidance on when to use this tool versus alternatives such as get_mesh_info or get_scene_info. There is no mention of appropriate contexts or exclusions, leaving the agent to infer usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.