Skip to main content
Glama

Get Key Light Intensity

get_key_light_intensity

Retrieve the current key light intensity value to prepare for precise relative adjustments or verify absolute settings.

Instructions

Get the current key 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

  • server.js:1164-1172 (registration)
    Registration of the get_key_light_intensity tool with MCP server, defining its title, description, and empty input schema
    mcpServer.registerTool(
      'get_key_light_intensity',
      {
        title: 'Get Key Light Intensity',
        description: 'Get the current key 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: {}
      },
  • Handler function for get_key_light_intensity - retrieves the current key light intensity from browser state via WebSocket, queries fresh state and formats response with metadata
      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.keyLight?.intensity ?? 0;
          
          return {
            content: [
              {
                type: 'text',
                text: formatStateResponse(intensity.toString(), 'Key light intensity', sessionId, metadata)
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: 'text',
                text: `Error retrieving key light intensity: ${error.message}`
              }
            ],
            isError: true
          };
        }
      }
    );
Behavior3/5

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

No annotations provided; description does not disclose behavioral traits beyond the basic read operation. It states the value range but omits details on idempotency, permissions, or side effects. Adequate but minimal.

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?

Two sentences with no extraneous information. Front-loaded with key purpose, then usage guidelines. Efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Low-complexity tool with empty input schema and no output schema. Description adequately covers the value range and provides practical usage context, making it complete for the tool's purpose.

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?

No parameters in input schema; description adds no param details as none are needed. Baseline score of 4 for zero-parameter tool.

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?

Clearly states 'Get the current key light intensity value (0.0 or higher)', specifying verb, resource, and value range. Distinguishes from sibling tools that set or modify light intensity.

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?

Explicitly advises to query before relative intensity changes for accuracy, and suggests using cached state for absolute changes if no manual interactions. Provides clear when-to-use guidance.

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