Skip to main content
Glama

get_collection_info

Retrieve details about a named Blender collection to inspect its contents and properties before organizing or modifying scene objects.

Instructions

Get collection details.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and delivers almost nothing. It does not confirm the operation is non-destructive, does not state what happens when the named collection does not exist, and gives no sense of result size or cost.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no wasted words, but the brevity comes from under-specification rather than economy. There is room for a clause defining what details are returned without bloat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be spelled out, but that is the only gap covered. With zero annotation coverage and an undocumented required parameter, the definition leaves an agent unable to confirm input format or failure behavior before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — the single required parameter "name" has no description anywhere. The description never clarifies whether "name" is the collection's display name, an internal identifier, or a path, which is the one piece of meaning an agent most needs here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get collection details" states a verb and resource, so the agent knows this is a read of a single collection rather than the list returned by get_collections. But "details" is undefined — it does not say whether that means objects contained, membership, transforms, or metadata, which is exactly the ambiguity an agent faces next to siblings like get_collections and get_scene_info.

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 when-to-use guidance, no mention of the list-vs-single-collection distinction, and no note that the collection must already exist. The only hint is the word "Get" and the singular resource in the name, which the agent must infer.

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