Skip to main content
Glama

get_python_api_docs

Read-only

Find Python API identifiers or discover qualified matches with a trailing wildcard to look up Blender documentation.

Instructions

Find a Python API identifier or discover qualified identifiers with a trailing wildcard.

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": {
      "identifier": "<identifier>"
    },
    "name": "get_python_api_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNo
identifierYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar is lower. The description usefully discloses the two modes (exact identifier lookup vs wildcard discovery), but says nothing about result limits, case sensitivity, or whether repeated calls with different index values page through results. With annotations carrying the safety story, a 3 fits.

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?

A single front-loaded sentence with no filler, and the key mode distinction is stated early. It is concise to the point of under-specification rather than padded.

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?

An output schema exists, so return-value explanation is not required, but for a two-parameter lookup tool with zero schema coverage the description leaves the index parameter undocumented and provides no routing against sibling search tools. The core invocation (what a wildcard returns, how to iterate) remains guesswork.

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 must carry parameter meaning and largely fails to. It explains the wildcard convention for identifier but never mentions the index parameter at all, leaving an agent to guess that it selects among multiple matches or pages results.

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 names a verb (find/discover) and a resource (Python API identifier), and the trailing-wildcard clause hints at exact-match vs discovery modes. But it never clarifies whether the tool returns documentation, signatures, or merely identifier paths, and it does not distinguish itself from the existent sibling search_api_docs. An agent can guess the shape but not confidently separate it from the search tool.

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 when-to-use statement, no when-not-to-use, and no mention of the obvious alternative search_api_docs. The only implicit guidance is that a trailing wildcard triggers discovery mode, which is a mode hint rather than a routing rule.

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