Skip to main content
Glama

Dolly Camera In

dolly_camera_in

Move the camera closer to the subject in a 3D scene to adjust viewing distance and focus on specific elements.

Instructions

Move the camera closer to the subject (dolly in)

Input Schema

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

Implementation Reference

  • server.js:1580-1604 (registration)
    Tool registration and handler for dolly_camera_in - moves camera closer to subject with optional amount parameter
    mcpServer.registerTool(
      'dolly_camera_in',
      {
        title: 'Dolly Camera In',
        description: 'Move the camera closer to the subject (dolly in)',
        inputSchema: {
          amount: z.number().positive().optional().describe('Optional amount to move closer (defaults to configured dolly speed)')
        }
      },
      async ({ amount }) => {
        routeToCurrentSession({
          type: 'dollyCameraIn',
          amount: amount
        });
    
        return {
          content: [
            {
              type: 'text',
              text: amount ? `Camera moved ${amount} units closer` : 'Camera moved closer'
            }
          ]
        };
      }
    );
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 closer') but doesn't describe what happens if the camera hits limits, whether this affects other camera settings, or what the visual outcome is. 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 clearly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded with the essential information.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'closer' means in practical terms, what happens at minimum distance, whether this affects FOV or other camera properties, or what visual feedback to expect. The context signals indicate this is a simple tool, but more behavioral context would be helpful.

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 single optional parameter 'amount' with its type, constraints, and default behavior. The description doesn't add any parameter semantics beyond what's in the schema, meeting the baseline for high schema coverage.

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 closer to the subject') and specifies the type of movement ('dolly in'), which is a specific verb+resource combination. However, it doesn't explicitly differentiate from its sibling 'dolly_camera' or 'dolly_camera_out', which would be needed for a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'dolly_camera' or 'dolly_camera_out', nor does it mention any prerequisites or contextual constraints. It simply states what the tool does without 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