Skip to main content
Glama

Increase Camera Field of View

increase_camera_fov

Widen the camera's field of view to see more of the 3D scene. Specify an optional amount to adjust the viewing angle.

Instructions

Increase the camera field of view (wider angle, see more of the scene)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountNoOptional amount to increase (defaults to configured FOV speed)

Implementation Reference

  • server.js:1658-1682 (registration)
    Registration of the 'increase_camera_fov' tool with its input schema
    mcpServer.registerTool(
      'increase_camera_fov',
      {
        title: 'Increase Camera Field of View',
        description: 'Increase the camera field of view (wider angle, see more of the scene)',
        inputSchema: {
          amount: z.number().positive().optional().describe('Optional amount to increase (defaults to configured FOV speed)')
        }
      },
      async ({ amount }) => {
        routeToCurrentSession({
          type: 'increaseCameraFOV',
          amount: amount
        });
    
        return {
          content: [
            {
              type: 'text',
              text: amount ? `Camera FOV increased by ${amount}` : 'Camera FOV increased (wider angle)'
            }
          ]
        };
      }
    );
  • Handler function for the 'increase_camera_fov' tool - sends 'increaseCameraFOV' command via WebSocket and returns a text response
      async ({ amount }) => {
        routeToCurrentSession({
          type: 'increaseCameraFOV',
          amount: amount
        });
    
        return {
          content: [
            {
              type: 'text',
              text: amount ? `Camera FOV increased by ${amount}` : 'Camera FOV increased (wider angle)'
            }
          ]
        };
      }
    );
Behavior2/5

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

No annotations available, so description carries full burden. Discloses only that it increases FOV, but no details about default increment, limits, or 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?

Single sentence is concise and direct. However, lacks structure like bullet points or clear separation of key info.

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?

Adequate for a simple tool with one optional parameter and no output schema. However, missing behavioral details that would help an agent understand the tool's impact fully.

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 has 100% coverage for 'amount' parameter with clear description. Tool description adds no extra parameter info, but schema already suffices, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (increase), resource (camera field of view), and result (wider angle, see more). It distinguishes from siblings like 'decrease_camera_fov' via the verb.

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 on when to use this tool versus alternatives like 'set_camera_fov' or 'decrease_camera_fov'. No context about default behavior or prerequisites.

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