Skip to main content
Glama

capture_multiple_angles

Capture orthographic and perspective views from multiple angles to inspect and verify 3D work. Specify angles and max size to generate consistent visual references.

Instructions

Capture multiple orthographic/perspective angles.

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

Input Schema

NameRequiredDescriptionDefault
anglesNo
max_sizeNo

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?

With no annotations, the description carries the full behavioral burden, yet it discloses almost nothing. It does not say whether this is a read-only render operation, how many images are produced, whether outputs are written to disk, or what the default angle set is when the optional angles parameter is omitted.

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?

The single short sentence is front-loaded and waste-free, but its brevity reflects under-specification rather than efficient communication. There is no structure beyond a noun phrase.

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 explained, but for a tool with two undocumented optional parameters and zero annotations, the description leaves too much unanswered for an agent to call it confidently.

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 description coverage is 0%, so the description must compensate, and it does not. "angles" is only echoed as a concept (no format, no allowed values, no default behavior), and the max_size parameter is never mentioned at all.

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?

The description gives a verb ("Capture") and a resource (orthographic/perspective angles), and the word "multiple" hints it differs from single-view siblings like capture_camera_view or capture_viewport. But it never states what is actually captured (renders? images? files?) or explicitly distinguishes itself from those siblings, so the purpose stays vague.

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 at all: no mention of when multiple angles are preferable to a single capture tool, no prerequisites, and no alternatives named. The agent must infer the use case from the title alone.

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