Skip to main content
Glama
Sign In
mcp-for-cascadeur

mcp-for-cascadeur

by Rickcy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

camera_frame

Destructive

Frames named objects by their actual Transform positions and lets you inspect the resulting image framing, helping verify camera views before rendering.

Instructions

Frame actual Transform positions of named objects; inspect image framing afterwards.

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": {
      "objects": "<objects>"
    },
    "name": "camera_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectsYes
distance_scaleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety bar is lower, yet the description never confirms that the camera transform is overwritten or whether the prior view can be restored. The only behavioral addition is the suggestion to visually verify the result afterward, which is a workflow hint rather than disclosure of side effects.

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

Conciseness4/5

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

A single front-loaded sentence with no padding or redundancy. Its brevity costs clarity in places, but nothing in it is wasted text.

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?

No output schema exists, so return values need not be described, and the array-of-names behavior is inferable. However, for a destructive camera-mutating tool with two undocumented parameters, the definition omits side effects, reversibility, and any recovery or snapshot sibling to use beforehand.

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 only partly does: 'named objects' confirms the array holds object names. The distance_scale parameter (1-20) is completely unexplained, leaving the agent to guess whether it is a zoom factor, distance multiplier, or framing tightness.

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 verb 'Frame' plus the target 'named objects' gives a rough idea, but 'actual Transform positions' is engine jargon and the description never states plainly that this moves the camera to fit the objects in view. It also fails to distinguish itself from siblings like camera_set or viewport_capture, which an agent could easily confuse with it.

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 statement and no named alternative. The clause 'inspect image framing afterwards' hints at a verify-after workflow, but it doesn't say when to prefer this over camera_set or viewport_capture, nor any prerequisite such as a valid object selection.

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