Skip to main content
Glama
Sign In
HPR Knowledge Base MCP Server

HPR Knowledge Base MCP Server

by macsplit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

get_episode

Read-only

Retrieve detailed episode information, including transcript and comments, from Hacker Public Radio by episode ID.

Instructions

Get detailed information about a specific HPR episode including transcript if available

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": {
      "episodeId": "<episodeId>"
    },
    "name": "get_episode"
  }
}

Input Schema

NameRequiredDescriptionDefault
episodeIdYesEpisode ID number
includeTranscriptNoInclude full transcript if available (default: true)
includeCommentsNoInclude community comments (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true (safe read) and openWorldHint=true (results may vary). The description adds that transcript may be included if available, but doesn't disclose other behavioral details like rate limits or auth needs. It is consistent with annotations and adds moderate context.

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 clear sentence, front-loaded with the verb 'Get', no wasted words. Efficient and to the point.

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?

No output schema exists, so the description should clarify what 'detailed information' includes beyond transcript. It mentions transcript but not other likely fields (host, series, date, etc.). With siblings, it's somewhat complete but could be more specific.

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 coverage is 100% with each parameter described. The description reinforces the 'includeTranscript' parameter but adds no new semantic information beyond the schema. Baseline 3 is appropriate.

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?

The description clearly states the tool retrieves detailed information about a specific HPR episode, including transcript if available. It distinguishes from siblings like search_episodes (which is for searching) and get_host_info/get_series_info (which target different resources).

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?

The description implies usage when you have an episode ID and want detailed info. It doesn't explicitly exclude alternatives, but the context from siblings makes it clear. A slightly more explicit 'when to use' statement would improve it.

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

Deploy Server

Other Tools