Skip to main content
Glama

search_licences

Search Ofcom's UK radio licence register by frequency, range, emission code, licensee, postcode, or coordinates with radius. Returns licensee, grid reference, coordinates, licence type and frequencies per site.

Instructions

Search Ofcom's register of licensed UK radio sites (free). Filters are combined. freq_mhz: exact channel, e.g. 456.6375. freq_min_mhz/freq_max_mhz: a range. emission: e.g. 12K5G7W (12.5 kHz digital). licensee: name substring. postcode or lat/lon plus radius_km: only sites within that distance, nearest first. Returns licensee, grid ref, lat/lon, licence type and frequencies per site.

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

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
limitNo
emissionNo
freq_mhzNo
licenseeNo
postcodeNo
radius_kmNo
freq_max_mhzNo
freq_min_mhzNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 behavioral burden; it does disclose that the source is free and lists the returned fields per site, plus result ordering for geo queries. It says nothing about rate limits, pagination beyond the undocumented limit parameter, or how a missing/ambiguous postcode is handled, which is a notable gap for a 10-parameter query tool.

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?

Front-loads the purpose in one sentence, then uses compact 'param: meaning' fragments so each line earns its place with no filler. Return fields are summarized in a single closing sentence rather than enumerated at length.

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 10-parameter tool with no annotations and no output schema, the description covers nine parameters' meaning and previews the return shape, which is enough to invoke it correctly. The residual gaps are the undocumented limit parameter and the absence of stated constraints when both freq_mhz and the min/max range are supplied together.

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 description coverage is 0%, so the description must compensate and largely does: it explains the exact-vs-range frequency parameters, gives a concrete emission code example with its meaning ('12K5G7W (12.5 kHz digital)'), defines licensee as a substring match, and ties postcode/lat/lon to radius_km with a distance rule. Only limit is left undocumented.

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: 'Search Ofcom's register of licensed UK radio sites', with the domain (UK radio licensing) made explicit. It is clearly distinguishable in content from a licensee-lookup sibling, but it never names an alternative tool to route against, so it stops short of full sibling differentiation.

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?

'Filters are combined' tells the agent filters are ANDed rather than alternatives, and 'nearest first' documents the geospatial ordering. It also implicitly presents freq_mhz as exact-match versus freq_min_mhz/freq_max_mhz as a range. What's missing is any when-not guidance or pointer to sibling tools such as search_licensee or repeaterbook_search.

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