Skip to main content
Glama
Sign In
GMA2 MCP

GMA2 MCP

by chienchuanw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_fixture_value

Adjust the dimmer level of one or multiple fixtures by specifying a fixture number and a percentage value, with optional range support.

Instructions

Set fixture(s) to a dimmer value.

Args:
    fixture_id: Fixture number (or start of range)
    value: Dimmer percentage (0-100)
    end_fixture: (Optional) End fixture for range

Returns:
    str: Operation result message

Examples:
    - Set fixture 1 to 75%
    - Set fixtures 1 thru 10 to 50%

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fixture_id": "<fixture_id>",
      "value": "<value>"
    },
    "name": "set_fixture_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixture_idYes
valueYes
end_fixtureNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only says 'Set fixture(s) to a dimmer value' with no disclosure of side effects, undoability, or permissions needed. Minimal transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with Args, Returns, and examples. It is slightly verbose for a simple tool but every sentence adds value. Could be more terse.

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, the description covers basic usage, parameter ranges, and return type. It lacks error handling or fixture existence checks, but is largely complete for the intended function.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema coverage is 0%, but the description adds meaning: fixture_id is 'Fixture number (or start of range)', value is 'Dimmer percentage (0-100)', end_fixture is 'Optional end fixture for range'. This fully clarifies parameter semantics.

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 'Set fixture(s) to a dimmer value' and provides examples for single and range fixtures. It distinguishes from siblings like set_fixture_attribute which handles 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 Guidelines3/5

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

The description implies usage through examples (setting single or range of fixtures to a percentage) but does not explicitly state when to use this tool vs alternatives like set_fixture_attribute or apply_preset.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools