Skip to main content
Glama

list_sources

Lists all available free and paid radio data sources, shows whether each is enabled, its cost, and the environment variables required to enable it.

Instructions

List every data source (free and paid), whether it is enabled, its cost, and the environment variables needed to enable 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": "list_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses what the response contains (per-source enabled state, cost, env vars), which substitutes for the missing output schema, but it does not state that the call is read-only, whether it performs network lookups, or whether env-var names could reveal sensitive configuration.

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?

A single front-loaded sentence that states the resource and every field returned, with no filler or redundancy. Nothing could be removed without losing information.

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 zero-parameter tool with no annotations and no output schema, the description is nearly complete because it effectively documents the return shape. A mild gap remains around whether the listing is static metadata or reflects live configuration state.

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?

The tool takes zero parameters, so there is nothing to disambiguate; the baseline of 4 applies. The description correctly implies the tool needs no arguments.

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 gives a specific verb ('List') and resource ('every data source') and enumerates the attributes returned: enabled status, cost, and required environment variables. It does not name or distinguish itself from any sibling, but the siblings (repeaterbook_search, search_licences, export_whistler) are clearly unrelated functions, so differentiation is not critical here.

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: the mention of 'environment variables needed to enable it' signals a configuration/diagnostic purpose, but there is no explicit 'use this when...' statement or exclusion. For a parameterless listing tool this is likely sufficient in practice, though the agent must infer the intent.

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