Skip to main content
Glama

Get Fill Light Position (Spherical Coordinates)

get_fill_light_position_spherical

Get the fill light position in camera-centric spherical coordinates to enable precise relative adjustments like rotation.

Instructions

Get the current fill light position in camera-centric spherical coordinates. Query this before relative position changes (e.g., "rotate light 10 degrees") 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:1355-1403 (registration)
    Registration and handler for the 'get_fill_light_position_spherical' tool using McpServer.registerTool. The tool queries browser state via WebSocket to get the fill light's spherical position (azimuth, elevation, distance).
    mcpServer.registerTool(
      'get_fill_light_position_spherical',
      {
        title: 'Get Fill Light Position (Spherical Coordinates)',
        description: 'Get the current fill light position in camera-centric spherical coordinates. ' +
          'Query this before relative position changes (e.g., "rotate light 10 degrees") 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 position = state.fillLight?.position || { azimuth: 0, elevation: 0, distance: 0 };
          const positionText = `azimuth ${position.azimuth}°, elevation ${position.elevation}°, distance ${position.distance}`;
          
          return {
            content: [
              {
                type: 'text',
                text: formatStateResponse(positionText, 'Fill light position', sessionId, metadata)
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: 'text',
                text: `Error retrieving fill light position: ${error.message}`
              }
            ],
            isError: true
          };
        }
      }
    );
Behavior3/5

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

No annotations are provided, so the description bears full responsibility. While it implies a safe read operation, it does not disclose any potential side effects, performance implications, or required permissions. For a simple getter, this is adequate but not thorough.

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?

Two sentences, front-loaded with purpose followed by usage guidance. Every sentence is meaningful and concise, earning its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (no parameters, no output schema), the description covers all necessary contextual information: what it returns, when to call it, and when context suffices. It is complete for the task.

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?

Tool has no parameters, so schema coverage is 100%. The description adds value by specifying the coordinate system (camera-centric spherical), enhancing understanding of the output without needing parameter explanation.

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 explicitly states the tool retrieves the fill light position in camera-centric spherical coordinates, clearly distinguishing its purpose from sibling tools that set or modify the position.

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

Usage Guidelines5/5

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

Provides explicit guidance: query before relative position changes for accuracy, and for absolute changes, context can be used if no manual interactions occurred. This clearly differentiates when to use this tool versus relying on cached state.

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