Skip to main content
Glama

Dolly Camera Out

dolly_camera_out

Move the camera farther from the subject to adjust perspective in 3D visualization scenes. Control camera distance for better viewing angles.

Instructions

Move the camera farther from the subject (dolly out)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountNoOptional amount to move farther (defaults to configured dolly speed)

Implementation Reference

  • The 'dolly_camera_out' tool handler is registered here. It moves the camera farther from the subject by sending a 'dollyCameraOut' command to the current session via WebSocket. The tool accepts an optional 'amount' parameter for distance and returns a text response confirming the movement.
    mcpServer.registerTool(
      'dolly_camera_out',
      {
        title: 'Dolly Camera Out',
        description: 'Move the camera farther from the subject (dolly out)',
        inputSchema: {
          amount: z.number().positive().optional().describe('Optional amount to move farther (defaults to configured dolly speed)')
        }
      },
      async ({ amount }) => {
        routeToCurrentSession({
          type: 'dollyCameraOut',
          amount: amount
        });
    
        return {
          content: [
            {
              type: 'text',
              text: amount ? `Camera moved ${amount} units farther` : 'Camera moved farther'
            }
          ]
        };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the action ('Move') but doesn't specify whether this is a reversible operation, if it requires specific permissions, what happens if the camera reaches limits, or what the expected outcome looks like. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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?

The description is a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a simple tool and front-loads the essential information ('Move the camera farther from the subject').

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?

Given the tool's simplicity (1 optional parameter, 100% schema coverage, no output schema), the description is minimally adequate. However, as a mutation tool with no annotations, it should ideally provide more behavioral context about what 'dolly out' means in practical terms, potential side effects, or relationship to other camera tools. The current description meets basic requirements but leaves room for improvement.

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 description coverage is 100%, so the schema already documents the 'amount' parameter thoroughly. The description doesn't add any additional meaning beyond what's in the schema (e.g., units, typical values, or practical effects). With complete schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to.

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 clearly states the action ('Move the camera farther from the subject') and the specific operation ('dolly out'), which is a precise verb+resource combination. However, it doesn't explicitly distinguish this from its sibling 'dolly_camera_in' (which presumably moves closer) or the more general 'dolly_camera', leaving some ambiguity about when to choose between these similar tools.

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?

No guidance is provided on when to use this tool versus alternatives like 'dolly_camera_in' or 'dolly_camera'. The description only states what it does, not when it should be selected over other camera movement tools in the sibling list, leaving the agent to infer usage context.

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