Skip to main content
Glama

Golova.Wiki — event equipment registry

get_item

Item card by canonical code (GW-XXXXXX): specifications, brand, section, compatible amplification.

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": {
      "code": "<code>"
    },
    "name": "get_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesCanonical code, e.g. GW-KBVNPE

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / code / description
      Previous value: -"канонический код, напр. GW-KBVNPE"New value: +"Canonical code, e.g. GW-KBVNPE"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully characterizes the response contents (specs, brand, section, amplification compatibility), signaling a read-only detail lookup, but says nothing about what happens when a code is unknown or malformed, nor about read-only guarantees or result cardinality.

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?

One compact sentence, front-loaded with the resource and key, with the returned fields listed after the colon. No filler, though the GW-XXXXXX format token duplicates the schema.

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 one-parameter read lookup with no output schema, the description is nearly sufficient: it conveys what the call returns and what key it needs. The main gap is failure behavior for a missing or invalid code.

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% and the single 'code' parameter is already documented with the same GW-XXXXXX example format, so the description mostly restates structured data. Baseline 3 applies; no extra semantics (e.g., case sensitivity, exact-match requirement) are added.

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 names the resource ('item card'), the lookup key ('canonical code'), and enumerates the payload ('specifications, brand, section, compatible amplification'). That is enough to distinguish a single-item fetch from search-style siblings like search_equipment, though it never explicitly contrasts with them.

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?

There is no statement of when to use this tool versus alternatives such as search_equipment or find_compatible. The only implied precondition is having a canonical code, which the schema already declares as required, so the description adds no routing guidance.

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