Skip to main content
Glama

radioreference_call

Call RadioReference SOAP methods with method names and parameters to retrieve radio system, county, or frequency data using configured credentials.

Instructions

Call a RadioReference SOAP method, e.g. getCountyInfo with {'ctid': 1234}. Needs RADIOREFERENCE_APP_KEY, _USERNAME, _PASSWORD and the [radioreference] extra.

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": {
      "method": "<method>"
    },
    "name": "radioreference_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodYes
paramsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 disclose auth requirements and an install-time dependency, which is genuine behavioral value. It does not say whether the underlying SOAP methods are read-only or mutating, what the response looks like, or how errors surface — meaningful gaps for a generic dispatch tool.

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?

Two tight sentences: the action and an inline example come first, prerequisites second. Every clause earns its place; only the line break and the bracketed extra name make it slightly less polished than ideal.

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

Completeness3/5

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

For a generic dispatch tool with no annotations, no output schema, and 0% schema coverage, the definition is minimally adequate: an agent knows what to call and what credentials it needs. It lacks any pointer to the method catalog or return shape, which an agent would need to actually use the passthrough without guessing.

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 0%, so the description must compensate; it explains that `method` is a SOAP method name and that `params` is a method-specific key/value object, e.g. {'ctid': 1234}. That clarifies structure but offers no way to discover which method names or param keys are valid, so half the compensation is missing.

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?

States a specific verb and resource ('Call a RadioReference SOAP method') and immediately grounds it with a concrete example ('getCountyInfo with {'ctid': 1234}'), so an agent understands this is a generic passthrough rather than a typed query. It does not differentiate from service-specific siblings such as radioid_api, which keeps it below a 5.

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: any RadioReference SOAP method goes through this tool. It adds useful prerequisites (RADIOREFERENCE_APP_KEY, _USERNAME, _PASSWORD, the [radioreference] extra) but gives no explicit when-to-use/when-not guidance or direction on choosing this over sibling lookup tools.

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