Skip to main content
Glama
Ref2Blender MCP Server

Ref2Blender MCP Server

by evarynstudio

scene_summary

Lists the objects in the Ref2Blender collection with their dimensions and triangle counts, so you can review model geometry and budget before export.

Instructions

List the objects in the Ref2Blender collection with dimensions and triangle counts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. 'List' implies a non-destructive read, and the mention of dimensions and triangle counts tells the agent what data is surfaced, but there is no statement about connection requirements, whether the collection must exist, or what happens when Blender is unavailable — all plausible failure modes given the sibling tool blender_status.

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 scoping constraint (Ref2Blender collection) comes before the returned data, which is the right order for an agent scanning for relevance.

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 zero-argument read tool with an output schema documenting the return shape, the description covers scope and payload adequately. The only meaningful gap is that it doesn't state whether the call presumes an active Blender session, which matters given the sibling status tool.

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 the baseline is 4; there are no parameter semantics to clarify. The description correctly avoids inventing arguments and focuses on scope instead.

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 and resource: list objects in the Ref2Blender collection, and names the data returned (dimensions, triangle counts). It clearly differs from write-oriented siblings like clear_model or export_model, but doesn't explicitly distinguish itself from inspection siblings such as check_model or blender_status.

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 explicit when-to-use guidance, no mention of prerequisites (e.g. an active Blender connection), and no reference to alternatives like check_model or blender_status. The agent must infer the context from the phrase 'in the Ref2Blender collection'.

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