Skip to main content
Glama

Nudge Fill Light Elevation Up

nudge_fill_light_elevation_up

Raises fill light elevation in a 3D scene by a specified number of degrees, after querying current position for accuracy.

Instructions

Adjust the fill light elevation upward relative to current position. This tool automatically queries fresh state before performing the adjustment to ensure accuracy, even if the user has manually moved the light.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
degreesNoAmount to increase elevation in degrees (defaults to 5°)

Implementation Reference

  • server.js:2599-2645 (registration)
    Registration of the 'nudge_fill_light_elevation_up' tool via mcpServer.registerTool. Defines title, description, input schema (optional degrees parameter), and the async handler that queries fresh state, routes the command 'nudgeFillLightElevationUp' to the browser session, and returns a text response.
    mcpServer.registerTool(
      'nudge_fill_light_elevation_up',
      {
        title: 'Nudge Fill Light Elevation Up',
        description: 'Adjust the fill light elevation upward relative to current position. ' +
          'This tool automatically queries fresh state before performing the adjustment to ensure accuracy, ' +
          'even if the user has manually moved the light.',
        inputSchema: {
          degrees: z.number().positive().optional().describe('Amount to increase elevation in degrees (defaults to 5°)')
        }
      },
      async ({ degrees }) => {
        const sessionId = getCurrentSessionId();
        if (!sessionId) {
          return {
            content: [
              {
                type: 'text',
                text: 'Error: No active session found.'
              }
            ],
            isError: true
          };
        }
    
        // Query fresh state before manipulation
        const state = await queryFreshStateForManipulation(sessionId);
        const currentPosition = state?.fillLight?.position || { azimuth: 0, elevation: 0, distance: 0 };
        const positionInfo = ` (from current elevation: ${currentPosition.elevation}°)`;
    
        routeToCurrentSession({
          type: 'nudgeFillLightElevationUp',
          degrees: degrees
        });
    
        return {
          content: [
            {
              type: 'text',
              text: degrees 
                ? `Fill light elevation increased by ${degrees}°${positionInfo}` 
                : `Fill light elevation increased by 5°${positionInfo}`
            }
          ]
        };
      }
    );
  • The handler function for the 'nudge_fill_light_elevation_up' tool. It validates the session, queries fresh state via queryFreshStateForManipulation, routes a 'nudgeFillLightElevationUp' command to the browser via routeToCurrentSession, and returns a descriptive text response indicating the elevation change (default 5° or user-specified degrees).
    'nudge_fill_light_elevation_up',
    {
      title: 'Nudge Fill Light Elevation Up',
      description: 'Adjust the fill light elevation upward relative to current position. ' +
        'This tool automatically queries fresh state before performing the adjustment to ensure accuracy, ' +
        'even if the user has manually moved the light.',
      inputSchema: {
        degrees: z.number().positive().optional().describe('Amount to increase elevation in degrees (defaults to 5°)')
      }
    },
    async ({ degrees }) => {
      const sessionId = getCurrentSessionId();
      if (!sessionId) {
        return {
          content: [
            {
              type: 'text',
              text: 'Error: No active session found.'
            }
          ],
          isError: true
        };
      }
    
      // Query fresh state before manipulation
      const state = await queryFreshStateForManipulation(sessionId);
      const currentPosition = state?.fillLight?.position || { azimuth: 0, elevation: 0, distance: 0 };
      const positionInfo = ` (from current elevation: ${currentPosition.elevation}°)`;
    
      routeToCurrentSession({
        type: 'nudgeFillLightElevationUp',
        degrees: degrees
      });
    
      return {
        content: [
          {
            type: 'text',
            text: degrees 
              ? `Fill light elevation increased by ${degrees}°${positionInfo}` 
              : `Fill light elevation increased by 5°${positionInfo}`
          }
        ]
      };
    }
  • Input schema for the tool: optional 'degrees' parameter (positive number, describing 'Amount to increase elevation in degrees (defaults to 5°)').
    inputSchema: {
      degrees: z.number().positive().optional().describe('Amount to increase elevation in degrees (defaults to 5°)')
    }
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that the tool 'automatically queries fresh state before performing the adjustment to ensure accuracy', which adds valuable behavioral context beyond the schema. It does not mention potential side effects or permissions, but for a simple nudge, this is sufficient.

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: first states the action, second adds behavioral note. Front-loaded, every word earns its place, and no superfluous content.

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?

For a simple tool with one optional parameter and no output schema, the description is adequate. It covers the action and a key behavioral detail (state freshness). It does not explain revert or state change, but given the tool's simplicity, it is sufficiently complete.

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 baseline is 3. The tool description does not add any parameter information beyond what the schema already provides (e.g., the default value of 5° is in the schema's description field). No extra meaning added.

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 ('adjust the fill light elevation upward') and specifies 'relative to current position', distinguishing it from the sibling tool 'nudge_fill_light_elevation_down'. The verb-resource pair is specific and unambiguous.

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

Usage Guidelines3/5

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

The description implies usage when wanting to increase fill light elevation, but provides no explicit guidance on when not to use it or alternatives among sibling tools (e.g., 'swing_fill_light_up', 'move_fill_light_toward_direction'). The context is clear but lacks exclusions or comparisons.

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