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

blender-mcp-master

by God-601
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_blender_skill

Retrieve the Blender MCP Master skill instructions (SKILL.md) to guide AI agents through a structured Blender modeling workflow.

Instructions

Return the Blender MCP Master agent skill instructions (SKILL.md).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_blender_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 provided, so the description carries the burden; 'Return' plus a zero-argument schema makes the read-only, side-effect-free nature reasonably clear. However, it says nothing about document size, format, whether content is static, or failure behavior — meaningful for a tool whose whole output is one long instruction document.

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?

A single front-loaded sentence with zero filler; the resource identifier is given immediately.

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 zero-parameter read with no output schema, the description is minimally sufficient — an agent can invoke it without further info. But it leaves the relationship to get_blender_reference / get_blender_mcp_setup and the nature of 'Master agent skill' content unexplained, which is the main remaining ambiguity.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline is 4. The description correctly implies the call needs no arguments.

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 ('Return') and a specific resource ('Blender MCP Master agent skill instructions (SKILL.md)'), so an agent knows exactly what payload to expect. It does not explicitly contrast itself with get_blender_reference or get_blender_mcp_setup, which are the closest-sounding siblings, so it stops short of a 5.

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?

There is no statement of when to call this versus the four sibling tools, and no prerequisites or exclusions. Usage is only inferable from the resource name itself.

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