Skip to main content
Glama

Swing Fill Light Up

swing_fill_light_up

Rotates the fill light in an upward arc around the model's center to adjust lighting angle.

Instructions

Rotate the fill light upward in an arc around the center of the model

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:837-858 (registration)
    Registration of the 'swing_fill_light_up' MCP tool using mcpServer.registerTool, with title 'Swing Fill Light Up' and description 'Rotate the fill light upward in an arc around the center of the model'
    mcpServer.registerTool(
      'swing_fill_light_up',
      {
        title: 'Swing Fill Light Up',
        description: 'Rotate the fill light upward in an arc around the center of the model',
        inputSchema: {}
      },
      async () => {
        routeToCurrentSession({
          type: 'swingFillLightUp'
        });
    
        return {
          content: [
            {
              type: 'text',
              text: 'Fill light swung up'
            }
          ]
        };
      }
    );
  • Handler function for 'swing_fill_light_up' that routes a 'swingFillLightUp' command to the current session's browser client via WebSocket, and returns a text response confirming 'Fill light swung up'
    async () => {
      routeToCurrentSession({
        type: 'swingFillLightUp'
      });
    
      return {
        content: [
          {
            type: 'text',
            text: 'Fill light swung up'
          }
        ]
      };
    }
  • Input schema for 'swing_fill_light_up' - an empty object ({}) as this tool takes no input parameters
    title: 'Swing Fill Light Up',
    description: 'Rotate the fill light upward 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 present. The description only describes the action without disclosing behavioral traits like step size, animation, or constraints. It lacks details that would help the agent understand 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 sentence of 11 words, no redundancy, and the action is front-loaded. Every word is necessary.

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 parameters and no output schema, the description is fairly complete. However, compared to similar tools like nudge_fill_light_elevation_up, it does not clarify the magnitude or nature of the rotation (e.g., step size vs continuous). The simplicity keeps complexity low.

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 no parameters, so baseline is 4. The description does not need to add parameter meaning, and it correctly states the action without mentioning parameters.

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), the target (fill light), and the direction (upward in an arc). It is specific and distinguishes from siblings like swing_fill_light_down or nudge_fill_light_elevation_up.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention context, prerequisites, or exclusions.

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