Skip to main content
Glama
Sign In
Rephonic

Rephonic

Official
by getrephonic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_episode

Retrieve detailed episode metadata including topics, locations, guests, and memorable moments using the episode ID.

Instructions

Look up metadata for an individual episode including topics, locations, guests, and memorable moments. Use an ID from the episode search or list_episodes tool.

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

Input Schema

NameRequiredDescriptionDefault
episode_idYesThe Rephonic episode ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It indicates a read-only operation ('look up metadata') and lists types of data returned. However, it does not disclose any additional behavioral traits such as authentication requirements, rate limits, or potential side effects. For a simple lookup, this is adequate but not exceptional.

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?

The description is two sentences with no redundant information. The first sentence front-loads the purpose and included data, and the second sentence provides usage guidance. Every word is necessary and earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one required parameter, no nested objects, no output schema), the description is complete. It explains what the tool does, what data it returns, and how to obtain the required input. There are no gaps for an AI agent to misunderstand.

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 sole parameter 'episode_id' is described in the schema as 'The Rephonic episode ID.' The tool description adds context by advising to use an ID from search or list_episodes tools, which provides meaningful guidance beyond the schema. Since schema coverage is 100%, the baseline is 3, and the added context raises it to 4.

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 clearly states the tool looks up metadata for an individual episode and lists example fields (topics, locations, guests, memorable moments). It distinguishes from siblings like list_episodes and search_episodes by mentioning using an ID from those tools. However, it does not explicitly differentiate from other lookup tools like lookup_podcast, so it's slightly less than perfect.

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 explicitly tells when to use this tool: 'Use an ID from the episode search or list_episodes tool.' This provides clear guidance on prerequisite information. It doesn't state when not to use it, but the context is sufficient for an AI agent to understand the appropriate scenario.

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