Skip to main content
Glama

lookup_dmr_id

Look up DMR radio IDs in RadioID.net's daily dump to identify amateur radio operators by callsign, ID, or country. Note that UK business radio IDs are not included.

Instructions

Look up DMR radio IDs in RadioID.net's daily dump (free). Amateur-focused: UK business radio IDs are not in it.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
countryNo
callsignNo
radio_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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, and it does disclose genuinely useful traits: the data comes from a daily dump (so results may be stale) and it is free of charge. It omits other behavior an agent needs, such as authentication requirements, rate limits, whether results are paginated, and what a match or miss 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?

Two tight sentences, front-loaded with the action and source, then the coverage caveat. No filler and nothing that could be cut without losing information.

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 four-parameter lookup tool with no annotations and no output schema, the description leaves key gaps: no explanation of any parameter, no return-value shape (single match vs list), and no guidance on combining filters. It covers the data source and its scope limits but not how to invoke it.

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% across four parameters (limit, country, callsign, radio_id), so the description must compensate and does not. Only the notion of a 'radio ID' loosely hints at the radio_id parameter; nothing explains call sign matching, country filtering format, or what limit bounds.

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 ('Look up DMR radio IDs') and names the data source (RadioID.net's daily dump), which is enough to distinguish it from a live API tool. It stops short of contrasting itself with the sibling radioid_api or other search tools, so it is clear but not fully differentiated.

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 implied rather than spelled out: '(free)' signals a low-cost bulk lookup and 'UK business radio IDs are not in it' tells the agent a coverage boundary where this tool will fail. However, no alternative is named for that excluded case and there is no explicit when-to-use/when-not-to-use statement.

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