Skip to main content
Glama

Move light source

move_light
Idempotent

Sets the simulator's light source to specific world coordinates, clamped to 42–758 × 42–478, so you can control lighting position.

Instructions

Move the light source to world coordinates (clamped to 42–758 × 42–478).

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

The annotations only declare idempotentHint=true. The description adds a useful behavioral constraint by stating that coordinates are clamped to 42–758 × 42–478, which is information beyond the annotation. However, it does not describe what happens when values are out of range beyond clamping, nor any return or failure behavior.

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 sentence with no wasted words. The action and coordinate clamp constraint are front-loaded and immediately useful.

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 two-parameter movement tool with an idempotent annotation and no output schema, the description provides enough context to call it correctly. Minor gaps remain around units and exact x/y-to-bound mapping, but the core behavior is covered.

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 0%, so the description must carry the burden. It identifies the values as 'world coordinates' and provides the clamping ranges, which adds meaning beyond the bare numeric x/y schema. It still does not explicitly map each bound to x or y or specify units, so compensation is partial.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Move the light source to world coordinates'. It is clear what the tool does, though it does not explicitly differentiate itself from any sibling tool because none of the listed siblings appear to move the light source.

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

Usage Guidelines2/5

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

The description implies that this tool is used to reposition the light source, but it gives no explicit guidance about when to use it versus alternatives or any prerequisites. No when-not-to-use conditions are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.