Skip to main content
Glama
Sign In
blender-mcp-master

blender-mcp-master

by God-601
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_blender_reference

Retrieves a bundled Blender modeling reference guide by its exact filename, letting AI agents load structured workflow instructions and validation resources before scripting.

Instructions

Read one bundled modeling reference guide by exact filename.

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

Input Schema

NameRequiredDescriptionDefault
nameYesExact .md filename from list_blender_resources.references

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Read' and 'bundled' do convey that this is a non-destructive read of static, shipped-in content, but nothing is said about what happens on a filename mismatch, document size, or the shape of the returned content.

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 zero filler; every word earns its place. It is arguably undersized rather than bloated, which is a completeness concern rather than a conciseness flaw.

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?

This is a simple single-parameter read tool with a fully documented input and no output schema, and the description makes clear it returns one bundled guide. The only meaningful omission is how it relates to the outline/excerpt siblings and what a bad filename produces.

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 coverage is 100% and the 'name' property already explains it must be an exact .md filename drawn from list_blender_resources.references. The description's phrase 'by exact filename' reinforces the exact-match requirement but adds no new meaning beyond the schema.

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?

States a specific verb (Read) and resource (bundled modeling reference guide) with the scope limited to 'one', so the agent knows it returns a single document rather than a listing. It only implicitly separates itself from siblings like get_blender_reference_outline and get_blender_reference_excerpt by implying the complete guide rather than an outline or excerpt.

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?

Usage is only implied: the agent can infer it should call this to read a guide's full content. There is no explicit guidance on when to prefer the outline or excerpt siblings, nor any stated prerequisite that the filename should come from list_blender_resources (that hint lives only in the schema).

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

Deploy Server

Other Tools