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 at once, expanding the visible area for better scene overview and navigation.

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)
    Tool registration for 'increase_camera_fov' - defines the tool's metadata (title, description), input schema (optional amount parameter), and the complete handler function that executes when the tool is called. The handler routes a command to the current browser session with type 'increaseCameraFOV' and returns a success message.
    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)'
            }
          ]
        };
      }
    );
  • The actual handler function for 'increase_camera_fov' (lines 1667-1682) that executes when the tool is invoked. It accepts an optional 'amount' parameter, routes the command to the current session via routeToCurrentSession(), and returns a formatted response indicating the FOV was increased.
    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)'
            }
          ]
        };
      }
    );
  • Helper function 'routeToCurrentSession' used by the increase_camera_fov handler to send commands to the appropriate browser WebSocket client. It retrieves the current session ID from AsyncLocalStorage context and forwards the command.
    function routeToCurrentSession(command) {
      const sessionId = sessionContext.getStore();
      if (sessionId) {
        console.error(`Routing command to session: ${sessionId}`, command.type);
        sendToSession(sessionId, command);
      } else if (isStdioMode) {
        // In STDIO mode, route to the unique STDIO session ID
        if (STDIO_SESSION_ID) {
          console.error(`Routing command in STDIO mode to session: ${STDIO_SESSION_ID}`, command.type);
          sendToSession(STDIO_SESSION_ID, command);
        } else {
          console.error('Routing command in STDIO mode - no session ID available, broadcasting to all clients:', command.type);
          if (wsClients.size > 0) {
            broadcastToClients(command);
          } else {
            console.error('No WebSocket clients connected. Command not routed:', command.type);
          }
        }
      } else {
        console.warn('Tool handler called but no session context available. Command not routed.');
        console.warn('Current request session ID:', sessionId);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool increases FOV but doesn't mention whether this is a persistent change, whether there are limits to how much FOV can be increased, what happens if the amount exceeds valid bounds, or what the tool returns (if anything). The description provides basic function but lacks important behavioral context for a mutation tool.

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?

The description is appropriately concise - a single sentence that efficiently communicates the core function. It's front-loaded with the main purpose and includes a clarifying parenthetical. There's no wasted verbiage, though it could potentially be structured to include more contextual 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 insufficiently complete. It explains what the tool does at a basic level but doesn't address important contextual questions: what happens after execution, whether changes are immediate or require confirmation, what errors might occur, or how this tool relates to other camera FOV tools in the sibling list.

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 'amount' parameter with its type, constraints, and default behavior. The description doesn't add any parameter-specific information beyond what's in the schema. According to the rubric, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 tool's purpose: 'Increase the camera field of view' with the explanation 'wider angle, see more of the scene'. It uses a specific verb ('increase') and resource ('camera field of view'), but doesn't explicitly differentiate from its sibling 'decrease_camera_fov' beyond the opposite direction implied by the name.

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. There's no mention of when to use 'increase_camera_fov' versus 'set_camera_fov' (which presumably sets an absolute value) or 'get_camera_fov' (which retrieves the current value). The description only explains what the tool does, not when it's appropriate.

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