Skip to main content
Glama

Golova.Wiki — event equipment registry

find_compatible

What fits an item and what it fits: compatibility links (stands, amplifiers, cases, cables, accessories, consumables) with conditions and trust level, plus amplifiers and processors named in the specs. By code.

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": "find_compatible"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesCanonical item code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / code / description
      Previous value: -"канонический код позиции"New value: +"Canonical item code"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add genuine signal beyond the schema: results include conditions and a trust level, and cover both directions of compatibility plus spec-named amplifiers/processors. It stops short of explaining what trust level or conditions mean, whether results can be empty, or how the two directions are distinguished in the response.

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 dense sentence that front-loads the bidirectional scope and then the payload categories, with no filler. The colon-and-parenthetical construction is slightly clunky to parse but every clause carries information.

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 lookup with no output schema and no annotations, the description conveys enough about the return payload (link records with conditions and trust level, plus spec-named gear) for an agent to decide to call it. The main residual gap is not defining trust level or the shape of a compatibility link.

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 coverage is 100% for the single required parameter, and the schema already documents it as a "Canonical item code". The description's "By code" merely restates this without adding format, sourcing, or lookup-failure semantics, so the baseline of 3 applies.

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 precisely — compatibility links for an item, in both directions ("what fits an item and what it fits") — and enumerates the categories covered (stands, amplifiers, cases, cables, accessories, consumables) plus spec-derived amplifiers/processors. It does not name or contrast any sibling (get_item, search_equipment), so an agent must infer the boundary itself.

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?

Usage is only implied: the agent can infer this is the tool for compatibility questions about a known item code. There is no statement of when to prefer it over get_item or search_equipment, and no exclusions or prerequisites (e.g. whether the code must already exist or whether unknown codes return empty).

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