Skip to main content
Glama

get_mesh_statistics

Retrieve mesh statistics for a named object or the entire Blender scene to inspect geometry counts and support modeling decisions.

Instructions

Get mesh statistics for an object or the whole scene.

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_mesh_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; 'Get' implies a non-destructive read, which is the main behavioral signal needed. It does not say what statistics are returned or whether they are aggregated, but an output schema exists and covers the return shape.

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?

One short sentence, no filler, with the resource stated first and the scope qualifier second. Nothing is redundant or buried.

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?

A low-complexity read tool with one optional parameter and a documented output schema needs little more than this, but the name-format ambiguity and the absence of any statistics content hint leave a small gap. Adding which name space 'name' refers to would complete it.

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 0% for the single optional 'name' parameter, so the description's 'for an object or the whole scene' is the only clue about its meaning. It still leaves open whether 'name' is an object name, a mesh datablock name, or how scene-wide mode is selected, leaving ambiguity an agent could trip on.

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?

Specific verb ('Get') plus resource ('mesh statistics') with the two scopes named: an object or the whole scene. It does not name a sibling tool it might be confused with, but none of the listed siblings compute mesh statistics, so confusion risk is low.

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?

The phrase 'for an object or the whole scene' implies the two modes but never states when to prefer this over get_object_info or get_scene_info, nor any prerequisites. An agent must infer that omitting the name yields scene-wide statistics.

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