Skip to main content
Glama

Dolly Camera

dolly_camera

Set the camera distance from the subject to control the dolly effect. Moves the camera closer or farther for adjusting perspective.

Instructions

Set the camera distance from the origin (dollying). Moves the camera closer or farther from the subject.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
distanceYesDistance from origin (camera position.z)
Behavior3/5

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

No annotations are provided, so description carries full burden. It discloses that the tool adjusts distance from origin along z-axis, but does not mention potential side effects or constraints beyond the schema's exclusiveMinimum.

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?

Two sentences, no redundant information. Each sentence adds value: first states purpose, second clarifies effect.

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 simple one-parameter tool with no output schema, the description covers purpose and basic behavior. It is serviceable but could mention that it sets an absolute value as opposed to incremental adjustments.

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 covers 100% of the parameter with description. The tool description adds context about 'dollying' and 'subject', which is helpful but not substantial additional meaning beyond schema.

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?

The description uses specific verb 'Set' and resource 'camera distance', and mentions 'dollying'. It clearly identifies the action. However, it does not explicitly differentiate from sibling tools like dolly_camera_in/out which are incremental.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for adjusting camera zoom ('closer or farther'), but does not specify when to use this absolute set versus incremental siblings, nor provides any exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aidenlab/hello3dmcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server