Skip to main content
Glama

repeaterbook_search

Search RepeaterBook's rest-of-world repeater listings by country, city, region, callsign, landmark, frequency, or mode (analog, DMR, NXDN, P25, TETRA) to locate radio repeater data.

Instructions

Search RepeaterBook's rest-of-world export (needs REPEATERBOOK_TOKEN and REPEATERBOOK_USER_AGENT). mode: analog, DMR, NXDN, P25 or tetra. % is a wildcard.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "repeaterbook_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
modeNo
regionNo
countryNoUnited Kingdom
callsignNo
landmarkNo
frequencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden, and it does disclose two real traits: authentication via REPEATERBOOK_TOKEN and REPEATERBOOK_USER_AGENT, and that % is a wildcard. It says nothing about result limits, pagination, ranking, or whether the call is read-only.

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?

Three dense sentences, front-loaded with the resource and credentials before the mode and wildcard details, with no filler. The telegraphic 'mode: analog...' fragment is terse to the point of being slightly harder to parse, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter, zero-annotation, no-output-schema tool, this is thin: an agent knows how to authenticate and what mode strings to use, but not how to format frequency, which location fields are mutually exclusive, what the defaults imply, or what comes back. Output schema being absent means the return shape is undocumented anywhere.

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

Parameters2/5

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

Schema description coverage is 0% for 7 parameters, so the description must compensate and largely does not. Only mode (analog/DMR/NXDN/P25/tetra) and the % wildcard get explained; city, region, country, callsign, landmark and especially frequency format are left entirely undefined, including which fields accept the wildcard.

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?

"Search RepeaterBook's rest-of-world export" pairs a specific verb with a specific resource and scope, and the mode list clarifies the kind of records involved. It does not differentiate itself from siblings like search_licences or search_licensee, so an agent must infer the boundary from the data source alone.

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 by the data source (search amateur/commercial repeaters worldwide). The description does not say when to prefer this over search_licences or radioreference_call, nor does it state prerequisites beyond the credential note. The credential requirement and the wildcard convention are helpful context but are not selection guidance.

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