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

blender-mcp-master

by God-601
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_blender_resources

List bundled Blender skill guides and reusable Python script templates so AI agents can find available modeling, validation, and export resources.

Instructions

List the skill reference guides and reusable Blender Python scripts bundled with this package.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations, so the description carries the load: 'bundled with this package' usefully implies a static, read-only local inventory rather than a live query. It does not state whether the listing is paginated, what identifying fields each entry exposes, or whether the returned names are the inputs the sibling get_* tools expect.

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 no filler. The scope qualifier 'bundled with this package' does real work and nothing is redundant.

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?

Simple zero-arg tool with no output schema, but the description leaves the crucial link unstated: that entries returned here are meant to be passed to get_blender_skill / get_blender_reference / get_blender_script. Naming that handoff would make it complete.

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?

Zero parameters and no schema properties, so the baseline of 4 applies; there is nothing for the description to disambiguate.

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?

Concrete verb 'List' plus a specific resource set: skill reference guides and reusable Blender Python scripts bundled with the package. It is distinguishable from the sibling get_blender_skill/get_blender_reference/get_blender_script tools by being the enumeration rather than the fetch, though that contrast is never stated.

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?

No explicit when-to-use or when-not statement, and no sibling tools are named. The discovery role (list first, then call a get_* tool for a specific item) is only implied by the word 'List' and the noun 'bundled'.

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