Skip to main content
Glama

Get Fill Light Intensity

get_fill_light_intensity

Retrieve the current fill light intensity value to accurately adjust lighting in 3D scenes. Use this tool before making relative intensity changes to ensure precise control over scene illumination.

Instructions

Get the current fill light intensity value (0.0 or higher). Query this before relative intensity changes (e.g., "increase by 0.5") 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 get_fill_light_intensity tool handler that retrieves the current fill light intensity from the browser state. It uses getCurrentSessionId() to get the session, queries state via getState(), extracts the intensity value, and returns it with metadata via formatStateResponse().
    mcpServer.registerTool(
      'get_fill_light_intensity',
      {
        title: 'Get Fill Light Intensity',
        description: 'Get the current fill light intensity value (0.0 or higher). ' +
          'Query this before relative intensity changes (e.g., "increase by 0.5") 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 intensity = state.fillLight?.intensity ?? 0;
          
          return {
            content: [
              {
                type: 'text',
                text: formatStateResponse(intensity.toString(), 'Fill light intensity', sessionId, metadata)
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: 'text',
                text: `Error retrieving fill light intensity: ${error.message}`
              }
            ],
            isError: true
          };
        }
      }
    );
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It effectively discloses key behavioral traits: it's a read-only operation (implied by 'Get'), returns a numeric value with a minimum constraint, and highlights the importance of fresh state for relative changes. However, it doesn't mention potential errors, latency, or side effects, leaving some gaps.

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 front-loaded with the core purpose in the first sentence, followed by two concise usage guidelines. Each sentence earns its place by providing critical context without redundancy. The structure is efficient and well-organized for quick comprehension.

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 the tool's simplicity (0 parameters, no annotations, no output schema), the description is largely complete. It covers purpose, usage, and return value semantics adequately. However, it lacks details on error conditions or system-specific behaviors, which could be relevant for robust agent operation.

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 no parameter documentation is needed. The description adds value by explaining the return value semantics ('current fill light intensity value') and its numeric range, which goes beyond the empty input schema. A baseline of 4 is appropriate as it compensates for the lack of output schema.

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 verb ('Get') and resource ('current fill light intensity value'), including the value range constraint ('0.0 or higher'). It distinguishes from sibling tools like 'set_fill_light_intensity' by focusing on retrieval rather than modification, making the purpose unambiguous.

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 intensity changes') and when alternatives are acceptable ('For absolute changes, you may use recently queried state from context'). It directly addresses the tool's role in ensuring accuracy for relative operations versus relying on cached state for absolute changes.

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