Skip to main content
Glama
aidenlab

Hello3DMCP Server

by aidenlab
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

Get Fill Light Color

get_fill_light_color

Retrieve the current fill light color as a hex code for 3D scenes. Use this to verify colors before making adjustments in Hello3DMCP Server's visualization environment.

Instructions

Get the current fill light color as a hex color code (e.g., "#ffffff"). Query this before relative color changes to ensure accuracy. For absolute changes, you may use recently queried state from context if no manual interactions occurred.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:1454-1501 (handler)
    The get_fill_light_color tool handler that retrieves the current fill light color from the 3D scene state. It gets the session ID, queries state from the browser, extracts the fill light color, and returns a formatted response with metadata about the query source and timestamp.
    mcpServer.registerTool(
  'get_fill_light_color',
  {
    title: 'Get Fill Light Color',
    description: 'Get the current fill light color as a hex color code (e.g., "#ffffff"). ' +
      'Query this before relative color changes to ensure accuracy. ' +
      'For absolute changes, you may use recently queried state from context if no manual interactions occurred.',
    inputSchema: {}
  },
  async () => {
    const sessionId = getCurrentSessionId();
    if (!sessionId) {
      return {
        content: [
          {
            type: 'text',
            text: 'Error: No active session found.'
          }
        ],
        isError: true
      };
    }

    try {
      const { state, metadata } = await getState(sessionId);
      const color = state.fillLight?.color || '#ffffff';
      
      return {
        content: [
          {
            type: 'text',
            text: formatStateResponse(color, 'Fill light color', sessionId, metadata)
          }
        ]
      };
    } catch (error) {
      return {
        content: [
          {
            type: 'text',
            text: `Error retrieving fill light color: ${error.message}`
          }
        ],
        isError: true
      };
    }
  }
);
  • server.js:1454-1461 (registration)
    Registration of the get_fill_light_color tool with its title, description, and empty input schema (no parameters required).
    mcpServer.registerTool(
  'get_fill_light_color',
  {
    title: 'Get Fill Light Color',
    description: 'Get the current fill light color as a hex color code (e.g., "#ffffff"). ' +
      'Query this before relative color changes to ensure accuracy. ' +
      'For absolute changes, you may use recently queried state from context if no manual interactions occurred.',
    inputSchema: {}

Tool Definition Quality

A4.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the tool as a read operation ('Get') and specifies the return format (hex color code), which is helpful. However, it doesn't mention potential errors, latency, or whether this operation requires specific permissions. The description adds some value but lacks comprehensive behavioral context.

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 perfectly concise and well-structured: two sentences that each serve a distinct purpose. The first sentence states the core functionality, and the second provides usage guidelines. There's no wasted language, and the information is front-loaded with the primary purpose.

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 read operation with 0 parameters and no output schema, the description provides good context: it specifies the return format (hex color code) and offers practical usage guidance. However, without annotations or output schema, it could benefit from mentioning potential error conditions or response structure. The description is mostly complete but has minor gaps.

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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of parameters. The description appropriately doesn't discuss parameters, focusing instead on usage context. A baseline of 4 is appropriate for a zero-parameter tool where the description adds value elsewhere without needing to compensate for parameter documentation gaps.

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 tool's purpose: 'Get the current fill light color as a hex color code (e.g., "#ffffff").' It specifies the exact resource (fill light color) and output format (hex color code), distinguishing it from sibling tools like get_fill_light_intensity or get_key_light_color by focusing on color retrieval specifically.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool: 'Query this before relative color changes to ensure accuracy.' It also offers an alternative approach: 'For absolute changes, you may use recently queried state from context if no manual interactions occurred.' This clearly differentiates usage scenarios and provides practical advice.

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