Blender Bridge

Look up Blender Python API

lookup_blender_api

Read-onlyIdempotent

Look up the real Blender Python API without touching the scene: types with their properties, enum values and functions, operator parameters, node input and output socket names, and which Blender versions have a name. Use it before code that relies on names you are not sure of, and after AttributeError, KeyError or TypeError. query: an exact name (ShaderNodeBsdfPrincipled, Material.use_nodes, bpy.ops.wm.obj_import, ShaderNodeBsdfPrincipled.Emission Color) or keywords (glare bloom). blender_version: the user's Blender version if known; otherwise the version from the latest scene state is used.

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": {
      "query": "<query>"
    },
    "name": "lookup_blender_api"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of matching API entries to return.
`query`	Yes	Exact Blender Python/API/node/socket name or relevant English keywords.
`blender_version`	No	Blender version to search; omitted uses the last known scene/runtime version when available.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026

addedInput schema / properties / blender_version / description

Added value: +"Blender version to search; omitted uses the last known scene/runtime version when available."

addedInput schema / properties / limit / description

Added value: +"Maximum number of matching API entries to return."

addedInput schema / properties / query / description

Added value: +"Exact Blender Python/API/node/socket name or relevant English keywords."

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds value: 'without touching the scene' confirms no state mutation, and the blender_version fallback ('the version from the latest scene state is used') discloses a non-obvious default resolution behavior. It stops short of describing result shape or how partial/ambiguous matches behave.

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?

The purpose leads, usage follows, and parameter notes close it out — a sensible front-loaded order with no filler sentences. It is dense and runs as a single block, so the parameter guidance is slightly buried rather than structurally separated.

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

Completeness4/5

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

For a three-parameter read-only lookup with no output schema, the description covers purpose, triggers, query forms, and version handling. The one gap is any hint about what a result looks like (match count, ambiguity, miss behavior), which the absence of an output schema means the description could have carried.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description earns more: it distinguishes exact-name queries (with four concrete examples spanning bpy.ops, data properties, and node socket names) from keyword queries ('glare bloom'), and explains the version-omitted default. The limit parameter is left to the schema, which is acceptable.

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

Purpose5/5

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

The description names a specific verb and resource ('Look up the real Blender Python API') and enumerates exactly what kinds of entries are returned: types/properties, enum values, functions, operator parameters, node socket names, and version availability. That enumeration makes it clearly distinct from prose-oriented siblings such as search_blender_manual without needing to name them.

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?

It gives explicit triggering conditions: use it before writing code that relies on uncertain names, and after AttributeError, KeyError or TypeError. What's missing is a stated alternative or exclusion — e.g. when to prefer search_blender_manual — so the routing guidance is clear but not exhaustive.

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

All Blender Bridge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?