Skip to main content
Glama

export_whistler

Generate a Whistler EZ Scan CSV of licensed UK radio sites from the Ofcom register, filtered by postcode or coordinates, radius, counties, and frequencies, for scanner import.

Instructions

Write a Whistler EZ Scan text-import CSV (Alpha Tag, Frequency, Mode=AUTO) of licensed UK sites from the Ofcom register. Alpha tag is the licensee name cut to 16 characters. Give postcode or lat/lon plus radius_km as the search area. counties (e.g. ['Shropshire', 'Telford and Wrekin']) further restricts to those local authorities. freq_mhz limits to specific channels. Default output is ~/Downloads/uk_radio_whistler.csv.

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

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
countiesNo
freq_mhzNo
postcodeNo
radius_kmNo
output_pathNo
freq_max_mhzNo
freq_min_mhzNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the load and does disclose real behavior: it writes a file, the columns produced, the 16-character alpha-tag truncation, Mode=AUTO, and the default output path ~/Downloads/uk_radio_whistler.csv. It omits overwrite semantics, whether the directory must exist, and any permission/rate considerations for the up-to-9-parameter export.

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?

The output-artifact and its column shape are front-loaded, followed by search-area and filter guidance in a compact six-sentence block. Slightly dense with example lists (counties) but no wasted filler.

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 nine-parameter file-writing tool with no annotations and no output schema, the description covers the core search and output default well. It falls short on the two frequency-bound parameters and output_path behavior, and says nothing about overwrite/file-existence behavior, which an agent needs before writing to disk.

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 explain all nine parameters. It clarifies lat/lon/postcode+radius_km as the search area, counties as local-authority filters, and freq_mhz as channel limitation, and it implies the output path via its default. But freq_min_mhz, freq_max_mhz, and output_path are never explained, leaving a third of the parameters undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a concrete verb and artifact — writing a Whistler EZ Scan text-import CSV with specific columns (Alpha Tag, Frequency, Mode=AUTO) — sourced from the Ofcom UK register. This clearly distinguishes it from siblings like search_licences, which return data rather than produce a scanner file.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains how to invoke it: give postcode or lat/lon plus radius_km as the search area, optionally narrow with counties or freq_mhz. It gives clear usage context but never states when to prefer it over search_licences/search_licensee or what to do instead.

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