Skip to main content
Glama

Get Camera Field of View

get_camera_fov

Retrieve the current camera field of view value to enable accurate adjustments in 3D visualization applications. Query before making relative FOV changes to maintain precision.

Instructions

Get the current camera field of view (FOV) value. Query this before relative FOV changes to ensure accuracy. For absolute changes, you may use recently queried state from context if no manual interactions occurred.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:1759-1806 (registration)
    Registration and handler for get_camera_fov tool - registered with mcpServer.registerTool, queries camera FOV state from browser via getState() and returns formatted response with metadata
    mcpServer.registerTool(
      'get_camera_fov',
      {
        title: 'Get Camera Field of View',
        description: 'Get the current camera field of view (FOV) value. ' +
          'Query this before relative FOV changes to ensure accuracy. ' +
          'For absolute changes, you may use recently queried state from context if no manual interactions occurred.',
        inputSchema: {}
      },
      async () => {
        const sessionId = getCurrentSessionId();
        if (!sessionId) {
          return {
            content: [
              {
                type: 'text',
                text: 'Error: No active session found.'
              }
            ],
            isError: true
          };
        }
    
        try {
          const { state, metadata } = await getState(sessionId);
          const fov = state.camera?.fov ?? 0;
          
          return {
            content: [
              {
                type: 'text',
                text: formatStateResponse(fov.toString(), 'Camera FOV', sessionId, metadata)
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: 'text',
                text: `Error retrieving camera FOV: ${error.message}`
              }
            ],
            isError: true
          };
        }
      }
    );
Behavior3/5

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

With no annotations provided, the description carries the full burden. It implies this is a read-only operation (consistent with 'Get'), but does not disclose behavioral traits such as error conditions, rate limits, or whether it requires specific permissions. It adds some context about accuracy and state usage, but lacks details on return format or potential 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently structured in two sentences, front-loaded with the core purpose and followed by practical guidance. Every sentence earns its place by providing essential information without waste, making it easy for an AI agent to parse and apply.

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?

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is largely complete for a read operation. It covers purpose and usage context well. However, it could be more complete by specifying the return value format or units (e.g., degrees), which would help the agent interpret results accurately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on usage context. A baseline of 4 is applied as it adds value without redundancy, though it could slightly elaborate on the output if needed.

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 specific action ('Get') and resource ('current camera field of view value'), distinguishing it from siblings like 'increase_camera_fov' or 'set_camera_fov' which modify rather than retrieve the value. It precisely defines what the tool does without ambiguity.

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

Usage Guidelines4/5

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

The description provides clear context on when to use it ('Query this before relative FOV changes to ensure accuracy') and mentions an alternative approach ('For absolute changes, you may use recently queried state from context if no manual interactions occurred'). However, it does not explicitly state when not to use it or compare it to all sibling tools like 'get_camera_distance'.

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