Skip to main content
Glama

Get Fill Light Size

get_fill_light_size

Retrieve the current fill light area dimensions (width and height) in units for 3D scene lighting. Use before adjusting relative size to maintain accuracy in 3D visualization applications.

Instructions

Get the current fill light area size (width and height in units). Query this before relative size 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

  • The tool handler for 'get_fill_light_size' - retrieves the current fill light area size (width and height in units) from the browser state and returns it as a formatted text response. The handler gets the current session ID, queries the state using getState(), extracts the fillLight.size (defaults to {width: 1, height: 1}), and formats the response with metadata including timestamp and source.
    mcpServer.registerTool(
      'get_fill_light_size',
      {
        title: 'Get Fill Light Size',
        description: 'Get the current fill light area size (width and height in units). ' +
          'Query this before relative size 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 size = state.fillLight?.size || { width: 1, height: 1 };
          const sizeText = `width ${size.width}, height ${size.height}`;
          
          return {
            content: [
              {
                type: 'text',
                text: formatStateResponse(sizeText, 'Fill light size', sessionId, metadata)
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: 'text',
                text: `Error retrieving fill light size: ${error.message}`
              }
            ],
            isError: true
          };
        }
      }
    );
  • server.js:1503-1551 (registration)
    Registration of the 'get_fill_light_size' tool using mcpServer.registerTool(), including title, description, and empty input schema (no parameters required).
    mcpServer.registerTool(
      'get_fill_light_size',
      {
        title: 'Get Fill Light Size',
        description: 'Get the current fill light area size (width and height in units). ' +
          'Query this before relative size 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 size = state.fillLight?.size || { width: 1, height: 1 };
          const sizeText = `width ${size.width}, height ${size.height}`;
          
          return {
            content: [
              {
                type: 'text',
                text: formatStateResponse(sizeText, 'Fill light size', sessionId, metadata)
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: 'text',
                text: `Error retrieving fill light size: ${error.message}`
              }
            ],
            isError: true
          };
        }
      }
    );
Behavior4/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 effectively communicates that this is a read-only query operation (implied by 'Get'), provides context about state accuracy concerns, and mentions the potential for using cached data. However, it doesn't specify error conditions, rate limits, or authentication requirements.

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 sized at two sentences, with the first stating the core purpose and the second providing essential usage guidance. Every word earns its place with no redundancy or unnecessary elaboration.

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 zero-parameter read operation with no output schema, the description provides excellent context about what the tool returns (width and height in units) and when to use it. The only minor gap is the lack of explicit mention of the return format structure, though 'width and height in units' gives reasonable indication.

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 empty parameter set. The description appropriately doesn't add parameter information, maintaining focus on the tool's purpose and usage. A baseline of 4 is appropriate for zero-parameter tools.

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 ('Get'), resource ('current fill light area size'), and output format ('width and height in units'). It distinguishes from sibling tools like 'get_fill_light_color' and 'get_fill_light_intensity' by focusing specifically on size dimensions rather than other attributes.

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 size changes to ensure accuracy') and when alternatives are acceptable ('For absolute changes, you may use recently queried state from context if no manual interactions occurred'). This gives clear context for tool selection versus relying on cached data.

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