Skip to main content
Glama

Golova.Wiki — event equipment registry

search_equipment

Search the equipment registry by model name, brand or code, ranked by relevance. Optionally narrow to a section (slug, e.g. line-array, moving-head).

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": {
      "query": "<query>"
    },
    "name": "search_equipment"
  }
}

Input Schema

NameRequiredDescriptionDefault
fitsNoItem code: return only what is compatible with it (optional)
limitNoHow many to return (1-20, default 10)
queryYesSearch query (model, brand, code)
sectionNoSection slug to narrow the search (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / fits / description
      Previous value: -"код модели: только то, что с ней совместимо (необязательно)"New value: +"Item code: return only what is compatible with it (optional)"
    • changedInput schema / properties / limit / description
      Previous value: -"сколько вернуть (1-20, по умолчанию 10)"New value: +"How many to return (1-20, default 10)"
    • changedInput schema / properties / query / description
      Previous value: -"Поисковый запрос (модель, бренд, код)"New value: +"Search query (model, brand, code)"
    • changedInput schema / properties / section / description
      Previous value: -"slug раздела для сужения (необязательно)"New value: +"Section slug to narrow the search (optional)"
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it does disclose the ranking model ('ranked by relevance'), which is meaningful behavior beyond the schema. It does not state that results are read-only, how many results come back by default beyond the schema's limit description, or anything about result shape.

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, front-loaded with what is searched and how results are ranked, followed by the optional narrowing behavior. No filler or redundant restatement of the tool name.

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 four-parameter read/search tool with fully documented parameters and no output schema, this is nearly complete. The main omission is any hint about the returned result shape or what happens with unspecific queries, which matters slightly given there is no output schema to consult.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds value by giving concrete section slug examples ('line-array', 'moving-head') that the schema does not. The 'fits' parameter is not mentioned in the description at all, leaving its role to the schema alone.

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 states a specific verb and resource ('Search the equipment registry') plus the searchable fields (model name, brand, code) and the ranking behavior. It is clear what the tool does, but it never distinguishes itself from siblings like find_compatible, which appears to overlap with the 'fits' capability.

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?

It gives an implicit usage hint by framing 'section' as an optional narrowing step, and the slug examples clarify that intent. However, there is no explicit when-to-use or when-not-to-use guidance, and no signal about how it relates to find_compatible for compatibility-driven lookups.

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