Skip to main content
Glama
Sign In

Blender Bridge

by com.blenderbridge
OverviewDiscussionsAdmin

Search Blender manual

search_blender_manual
Read-onlyIdempotent

Search the official Blender manual (offline copy of the current release, CC-BY-SA 4.0) without touching the scene: how a feature, modifier, node or render setting works, what an option does, where it is in the interface, and recommended workflows. Use lookup_blender_api for exact Python names instead. query: a few English words (bevel modifier segments, depth of field focus, light linking). Returns the best sections with excerpts and page links; link the page when you quote it to the user.

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": "search_blender_manual"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of matching manual sections to return.
queryYesEnglish feature or workflow keywords to search in the bundled Blender manual.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of matching manual sections to return."
    • addedInput schema / properties / query / description
      Added value: +"English feature or workflow keywords to search in the bundled Blender manual."
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/closed-world, but the description adds real context: the manual is an offline copy of the current release under CC-BY-SA 4.0, results are 'best sections with excerpts and page links', and the agent is instructed to link pages when quoting. It doesn't mention result ranking or pagination limits, but the added licensing/return-shape context goes beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose and the not-touching-the-scene constraint, then the alternative, then query guidance, then return shape and citation expectation. No filler sentences; each clause carries decision-relevant information.

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

Completeness5/5

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

With no output schema, the description compensates by describing the return value (best sections with excerpts and page links) and telling the agent how to use results (link the page when quoting). For a 2-parameter read-only search tool, nothing an agent needs to call it correctly is missing.

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 baseline is 3, but the description adds genuine semantic guidance for 'query': 'a few English words' plus concrete examples ('bevel modifier segments', 'depth of field focus', 'light linking') that show the expected phrasing and granularity — something the schema's 'English feature or workflow keywords' does not convey. 'limit' is left to the schema, hence not a 5.

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?

States a specific verb and resource (search the official Blender manual), the content covered (features, modifiers, nodes, render settings, UI locations, workflows), and explicitly contrasts with the sibling lookup_blender_api. An agent can pick it apart from the other lookup tool without opening a schema.

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

Usage Guidelines5/5

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

Names the alternative tool and the condition that selects it ('use lookup_blender_api for exact Python names instead'), and enumerates the query types this tool is for. Also states it works 'without touching the scene', which tells the agent this is a safe non-mutating knowledge lookup.

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

All Blender Bridge toolsInspect
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