Skip to main content
Glama

Set Key Light Distance

set_key_light_distance

Set the key light distance from the model origin while maintaining its current azimuth and elevation angles.

Instructions

Set the distance of the key light from the model origin. Preserves current azimuth and elevation angles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
distanceYesDistance from model origin (positive number, units)

Implementation Reference

  • server.js:2760-2784 (registration)
    Registration of the 'set_key_light_distance' tool via mcpServer.registerTool() with input schema (distance: positive number) and handler
    mcpServer.registerTool(
      'set_key_light_distance',
      {
        title: 'Set Key Light Distance',
        description: 'Set the distance of the key light from the model origin. Preserves current azimuth and elevation angles.',
        inputSchema: {
          distance: z.number().positive().describe('Distance from model origin (positive number, units)')
        }
      },
      async ({ distance }) => {
        routeToCurrentSession({
          type: 'setKeyLightDistance',
          distance: distance
        });
    
        return {
          content: [
            {
              type: 'text',
              text: `Key light distance set to ${distance} units`
            }
          ]
        };
      }
    );
  • Handler function for set_key_light_distance that routes a 'setKeyLightDistance' command to the current session's browser client via WebSocket
      async ({ distance }) => {
        routeToCurrentSession({
          type: 'setKeyLightDistance',
          distance: distance
        });
    
        return {
          content: [
            {
              type: 'text',
              text: `Key light distance set to ${distance} units`
            }
          ]
        };
      }
    );
Behavior3/5

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

No annotations present; description only notes preservation of angles. Does not disclose other behavioral details like instant execution or side effects, but adequate for a simple setter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is efficient and front-loaded, but slightly sparse.

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?

Given no output schema and single parameter, description is minimally complete but lacks mention of prerequisites or error conditions.

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 coverage is 100% and already describes the parameter well. Description adds no extra meaning beyond schema.

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 verb 'Set', resource 'key light', property 'distance', and reference 'model origin'. It also specifies that azimuth and elevation are preserved, distinguishing it from tools like set_key_light_position_spherical.

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?

Implicitly suggests use when wanting to change distance only without affecting angles, but lacks explicit when-to-use or comparisons with siblings.

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