Skip to main content
Glama

Rotate Fill Light Counterclockwise

rotate_fill_light_counterclockwise

Rotate the fill light counterclockwise to increase azimuth. Automatically adjusts from current position for precise lighting control.

Instructions

Rotate the fill light counterclockwise (increases azimuth) relative to current position. This tool automatically queries fresh state before performing the rotation to ensure accuracy, even if the user has manually moved the light.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
degreesNoAmount to rotate in degrees (defaults to 10°)

Implementation Reference

  • Handler function for the 'rotate_fill_light_counterclockwise' tool. Queries fresh state from the browser for the fill light position, then sends a 'rotateFillLightCounterclockwise' command to the browser. Responds with text describing the rotation (defaults to 10° if degrees not provided).
    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 azimuth: ${currentPosition.azimuth}°)`;
    
      routeToCurrentSession({
        type: 'rotateFillLightCounterclockwise',
        degrees: degrees
      });
    
      return {
        content: [
          {
            type: 'text',
            text: degrees 
              ? `Fill light rotated ${degrees}° counterclockwise${positionInfo}` 
              : `Fill light rotated 10° counterclockwise${positionInfo}`
          }
        ]
      };
    }
  • server.js:2551-2597 (registration)
    Registration of the 'rotate_fill_light_counterclockwise' tool with MCP server. Defines the tool name, title 'Rotate Fill Light Counterclockwise', description explaining it rotates the fill light counterclockwise (increases azimuth), and an optional 'degrees' input schema (positive number, defaults to 10°).
    mcpServer.registerTool(
      'rotate_fill_light_counterclockwise',
      {
        title: 'Rotate Fill Light Counterclockwise',
        description: 'Rotate the fill light counterclockwise (increases azimuth) relative to current position. ' +
          'This tool automatically queries fresh state before performing the rotation to ensure accuracy, ' +
          'even if the user has manually moved the light.',
        inputSchema: {
          degrees: z.number().positive().optional().describe('Amount to rotate in degrees (defaults to 10°)')
        }
      },
      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 azimuth: ${currentPosition.azimuth}°)`;
    
        routeToCurrentSession({
          type: 'rotateFillLightCounterclockwise',
          degrees: degrees
        });
    
        return {
          content: [
            {
              type: 'text',
              text: degrees 
                ? `Fill light rotated ${degrees}° counterclockwise${positionInfo}` 
                : `Fill light rotated 10° counterclockwise${positionInfo}`
            }
          ]
        };
      }
    );
  • Input schema for the tool: an optional 'degrees' parameter which is a positive number with default of 10°.
    inputSchema: {
      degrees: z.number().positive().optional().describe('Amount to rotate in degrees (defaults to 10°)')
Behavior3/5

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

With no annotations, the description adds value by disclosing that the tool queries fresh state before rotating. However, it does not disclose potential side effects, reversibility, or authorization requirements.

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 concise sentences: first states purpose, second adds behavioral detail. No redundancy or unnecessary words.

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 covers the action, direction, and automatic state refresh. It could be improved by noting the non-destructive nature, but overall it is adequate.

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 schema provides a description for the 'degrees' parameter, but the tool description adds the default value of 10°, which is not in the schema. This extra context improves usability.

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 specifies the action ('Rotate the fill light counterclockwise') and ties it to increasing azimuth, which distinguishes it from the clockwise sibling.

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 for rotating the fill light counterclockwise but does not explicitly state when to use this versus the clockwise variant or other fill light adjustments. No alternatives or exclusions are mentioned.

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