Skip to main content
Glama
aidenlab

Hello3DMCP Server

by aidenlab
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

Walk Fill Light Out

walk_fill_light_out

Moves the fill light away from the model center along the origin axis to adjust lighting.

Instructions

Move the fill light farther from the center of the model along the axis from the model origin

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:998-1019 (registration)
    Registration of the walk_fill_light_out tool via McpServer.registerTool
    mcpServer.registerTool(
  'walk_fill_light_out',
  {
    title: 'Walk Fill Light Out',
    description: 'Move the fill light farther from the center of the model along the axis from the model origin',
    inputSchema: {}
  },
  async () => {
    routeToCurrentSession({
      type: 'walkFillLightOut'
    });

    return {
      content: [
        {
          type: 'text',
          text: 'Fill light walked out'
        }
      ]
    };
  }
);
  • server.js:1005-1019 (handler)
    Handler function for walk_fill_light_out tool - routes a 'walkFillLightOut' command to the current user session and returns a confirmation message
      async () => {
    routeToCurrentSession({
      type: 'walkFillLightOut'
    });

    return {
      content: [
        {
          type: 'text',
          text: 'Fill light walked out'
        }
      ]
    };
  }
);
  • server.js:1000-1004 (schema)
    Schema/input definition for walk_fill_light_out - no input parameters required, just a title and description
    {
  title: 'Walk Fill Light Out',
  description: 'Move the fill light farther from the center of the model along the axis from the model origin',
  inputSchema: {}
},

Tool Definition Quality

A3.8/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behavior. It states the direction but does not mention increment amount, whether it's continuous, or any limits. The tool has no parameters, so the step size is fixed but undisclosed.

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?

Single sentence that is clear, precise, and free of unnecessary words. Perfectly concise for the operation described.

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?

Given no output schema and no parameters, the description is mostly sufficient. However, it omits the step magnitude (how far per call), which would be helpful for an agent to understand the effect. Still, the intent is clear.

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?

Input schema has zero parameters. The description doesn't need to explain parameters, and schema coverage is 100%. Baseline score of 4 applies.

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 specific action: moving the fill light farther from the model center along the origin axis. It distinguishes from sibling tools like walk_fill_light_in (closer) and walk_key_light_out (different 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?

The description implies the tool is for pushing the fill light outward, but lacks explicit guidance on when to use this vs. alternatives like set_fill_light_distance or when not to use it. No exclusion criteria or context provided.

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