Skip to main content
Glama

Golova.Wiki — event equipment registry

rig_metrics

Rig metrics for a list of item codes: total weight and power draw, plus a check for missing amplifiers.

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": {
      "codes": "<codes>"
    },
    "name": "rig_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
codesYesItem codes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / codes / description
      Previous value: -"коды позиций"New value: +"Item codes"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden of behavioral disclosure. It helpfully states the computed outputs, but it does not clarify whether the operation is read-only, how invalid item codes are handled, or what the response structure looks like.

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 a single front-loaded sentence with no redundant wording. Every phrase contributes to explaining what the tool computes.

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 one-parameter metrics tool with no output schema, the description adequately explains the main outputs. It could be slightly more complete by defining what constitutes a 'missing amplifier' or by specifying the return shape, but the essential information is present.

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

Parameters3/5

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

Schema description coverage is 100%, so the single parameter 'codes' is already documented in the input schema. The description restates that it accepts a list of item codes but adds no additional constraints, formats, or examples beyond that baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource and the specific metrics computed: total weight, power draw, and missing amplifiers for a list of item codes. It does not explicitly distinguish this tool from siblings such as get_item or find_compatible, which is why it falls short of a 5.

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

Usage Guidelines2/5

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

The description implies when the tool might be useful by stating what it computes, but it provides no explicit when-to-use guidance, prerequisites, or comparison to alternatives. An agent must infer that this is the right tool whenever aggregate rig metrics are needed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources