Skip to main content
Glama

Walk Key Light In

walk_key_light_in

Move the key light closer to the model's center along the axis from the origin to adjust lighting.

Instructions

Move the key light closer to the center of the model along the axis from the model origin

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:929-950 (registration)
    Registration of the 'walk_key_light_in' tool via mcpServer.registerTool() with title, description, input schema, and async handler.
    mcpServer.registerTool(
      'walk_key_light_in',
      {
        title: 'Walk Key Light In',
        description: 'Move the key light closer to the center of the model along the axis from the model origin',
        inputSchema: {}
      },
      async () => {
        routeToCurrentSession({
          type: 'walkKeyLightIn'
        });
    
        return {
          content: [
            {
              type: 'text',
              text: 'Key light walked in'
            }
          ]
        };
      }
    );
  • The async handler function that executes when walk_key_light_in is called. Routes a 'walkKeyLightIn' command to the current session via WebSocket and returns a text response 'Key light walked in'.
      async () => {
        routeToCurrentSession({
          type: 'walkKeyLightIn'
        });
    
        return {
          content: [
            {
              type: 'text',
              text: 'Key light walked in'
            }
          ]
        };
      }
    );
  • Input schema for walk_key_light_in - an empty object (no parameters required), defined inside the registerTool call.
      description: 'Move the key light closer to the center of the model along the axis from the model origin',
      inputSchema: {}
    },
Behavior2/5

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

No annotations provided, so the description must disclose behavior. It states the action but lacks details on step size, whether it is incremental or absolute, animation behavior, or any side effects. Without annotations, this is insufficient for an unfamiliar agent.

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?

A single, concise sentence that conveys the action without any redundant or unnecessary words. It is well-structured and front-loaded with the main action.

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

Completeness3/5

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

For a simple zero-parameter tool, the description is adequate but missing behavioral details like step size, whether it is animated, or if it clamps to bounds. Sibling tools are not referenced to clarify differences. No output schema, but return value is likely straightforward.

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 zero parameters, and schema coverage is 100% (empty). The description adds meaning beyond the schema by explaining what the tool does. For zero-parameter tools, baseline is 4, and no additional param info is 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?

Description clearly states the action: 'Move the key light closer to the center of the model along the axis from the model origin'. It specifies the verb 'move', the resource 'key light', and the direction/scope. This distinguishes it from sibling tools like 'walk_key_light_out' or 'swing_key_light_*'.

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 when-to-use or when-not-to-use guidance. The description implies usage for moving the key light inward, but does not mention alternatives like 'walk_key_light_out' for outward movement, nor does it suggest prerequisites or context.

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