Skip to main content
Glama

Fyyd Get Podcast

fyyd_get_podcast
Read-onlyIdempotent

Podcast metadata + recent episodes.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "podcast_id": 12345
    },
    "name": "fyyd_get_podcast"
  }
}

Input Schema

NameRequiredDescriptionDefault
podcast_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered externally. The description adds nothing beyond that: it does not define what 'recent' means (count or time window), nor note any rate limits or upstream auth behavior for this open-world lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two words and a plus sign — there is zero padding, but this is a fragment rather than concise prose, and the missing information is far more costly than the saved tokens. It is front-loaded only in the trivial sense that there is nothing else.

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

Completeness2/5

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

An output schema exists, so return shapes need not be explained, but the tool still requires an undocumented identifier and delivers an undefined 'recent episodes' scope. For a lookup tool whose only input is opaque, the description leaves the agent without enough to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter, so the description carries the full burden — and it never mentions podcast_id. It does not clarify whether the value is a fyyd internal ID, what format it takes, or how an agent should obtain one before calling.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment 'Podcast metadata + recent episodes' does convey the resource and roughly what comes back, but it omits an explicit verb and never distinguishes itself from siblings like get_podcast_by_url or fyyd_search_podcasts. An agent can guess it is a lookup by ID, but the definition does not say so.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all, and no exclusion or pointer to alternatives. The presence of get_podcast_by_url and fyyd_search_podcasts in the sibling set makes the absence of routing guidance a real gap, since it is unclear when an ID lookup is preferred over a URL lookup or a search.

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.