Skip to main content
Glama

Swing Key Light Right

swing_key_light_right

Rotates the key light in a rightward arc around the model center, enabling precise lighting adjustments for 3D scenes.

Instructions

Rotate the key light rightward in an arc around the center of the model

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:747-768 (registration)
    Registration and handler for the swing_key_light_right tool. Registers with MCP server, sends 'swingKeyLightRight' command to browser session, and returns success text.
    mcpServer.registerTool(
      'swing_key_light_right',
      {
        title: 'Swing Key Light Right',
        description: 'Rotate the key light rightward in an arc around the center of the model',
        inputSchema: {}
      },
      async () => {
        routeToCurrentSession({
          type: 'swingKeyLightRight'
        });
    
        return {
          content: [
            {
              type: 'text',
              text: 'Key light swung right'
            }
          ]
        };
      }
    );
  • Handler function for swing_key_light_right. Routes a 'swingKeyLightRight' command to the current browser session via WebSocket.
    async () => {
      routeToCurrentSession({
        type: 'swingKeyLightRight'
      });
    
      return {
        content: [
          {
            type: 'text',
            text: 'Key light swung right'
          }
        ]
      };
    }
  • Schema/definition for swing_key_light_right: no input parameters, title 'Swing Key Light Right'.
    {
      title: 'Swing Key Light Right',
      description: 'Rotate the key light rightward in an arc around the center of the model',
      inputSchema: {}
    },
Behavior2/5

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

No annotations are provided, and the description only states the basic action. It does not disclose any behavioral traits such as whether rotation is incremental, angular limits, or 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 a single, concise sentence with no unnecessary words. It is front-loaded with the key information.

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 no parameters and no output schema, the description is sufficient. It could mention incremental nature or typical angle, but is otherwise complete.

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 tool has zero parameters, and schema coverage is 100% (vacuously). The description does not need to add param info. Baseline 4 is appropriate as there is nothing to improve.

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 ('rotate') and the resource ('key light'), with additional spatial detail ('rightward in an arc around the center of the model'). It is easily distinguishable from siblings like swing_key_light_left.

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?

No explicit guidance on when to use this tool versus alternatives. However, the sibling set is well-organized by naming convention, making the usage implicit. Lacks when-not or alternative suggestions.

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