Skip to main content
Glama

Development Radio

List Development Radio episodes

list_episodes
Read-only

Lists Development Radio episodes, newest first, each with its id, title, date, length, lanes, page URL, one-line description and the URLs of the primary sources it cites. Use this when you need the most recent episodes, an overview of what the show has covered, or a valid episode id for get_episode or get_transcript. The show's hosts are AI-generated voices.

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_episodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
laneNoOnly episodes in this lane of the show.
limitNoMaximum number of episodes to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds value beyond them: return ordering, the exact field set, and the caveat that hosts are AI-generated voices, which matters for how an agent should treat the content. It does not mention pagination behavior or what happens when limit is capped.

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?

Three front-loaded sentences: capability and return shape first, usage second, caveat last. Tight overall; the closing note on AI-generated voices is slightly tangential but does carry useful context.

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?

With no output schema, the description carries the return-value burden well by enumerating the fields each episode includes, and it explains ordering and typical use cases. The remaining gap is what happens at the limit boundary (default 10, max 50) and whether results are ever truncated.

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 100%, so both lane and limit are already documented with enum values and bounds. The description only alludes to "lanes" as a returned field and adds no filtering semantics or default/cap behavior beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ("Lists Development Radio episodes") plus the ordering (newest first) and the exact fields returned, which lets an agent distinguish it from get_episode and get_transcript without opening any schema.

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?

Gives concrete when-to-use triggers (recent episodes, overview of coverage, obtaining a valid episode id for get_episode/get_transcript) and points to the follow-on tools. It stops short of stating when NOT to use it, notably no routing guidance toward search_episodes for topical lookup.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.