Skip to main content
Glama

describe_api

Search installed Blender operators or inspect operator/RNA type schemas, enums, and defaults to confirm API details without eval.

Instructions

Discover installed operators or inspect real RNA property schemas, enums and defaults.

Omit name and use query to search operators, e.g. export or mesh. Give an exact
operator (mesh.primitive_cube_add) or RNA type (Object) for its schema. No eval.

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": {
      "session_id": "<session_id>"
    },
    "name": "describe_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
limitNo
queryNo
offsetNo
categoryNooperator
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add useful behavioral constraints, notably 'No eval' and the promise that schemas are 'real' runtime values rather than static stubs. But it does not disclose pagination behavior despite limit/offset params, says nothing about session requirements for session_id, and does not describe error behavior when a name is not found.

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?

Four short sentences, front-loaded with the purpose followed by the two usage modes. There is no filler. That said, the final sentence fragment 'No eval.' is abrupt and could be attached more clearly to the behavior it constrains.

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?

For a six-parameter tool with no annotations and no output schema, the description covers the central discovery and inspection flows but omits pagination semantics and the required session_id. It is adequate to make a first correct call, but not complete for repeated or paged 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 description coverage is 0%, so the description must compensate. It explains the two most important parameters, name and query, with concrete examples (mesh.primitive_cube_add, Object, 'export'), implying the category switch between operator and type. It leaves limit, offset, and the required session_id entirely undocumented, so coverage is only partial.

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 description states a specific verb and resource pair, 'Discover installed operators' and 'inspect real RNA property schemas, enums and defaults,' and it distinguishes two modes: operator discovery and type inspection. It never names a sibling like run_operator or inspect_object, but the two-mode distinction is clear enough to identify what this tool does.

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

Usage Guidelines3/5

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

It gives concrete instructions for its two invocation modes: omit name and use query to search, or give an exact operator or RNA type. That is parameter-mode guidance rather than routing between this tool and alternatives; nothing says when to use describe_api instead of run_operator or inspect_object, and no prerequisites are stated.

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