Skip to main content
Glama

Fyyd Top Podcasts

fyyd_top_podcasts
Read-onlyIdempotent

Return the most popular podcasts on fyyd, optionally filtered by category slug and language code, with up to 30 results per call.

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": {
      "category": "news"
    },
    "name": "fyyd_top_podcasts"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
countNo
categoryNoCategory slug from `categories`

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely new behavioral fact: results are capped at 30 per call, which the schema does not state. It says nothing about ranking criteria, ordering, or pagination beyond that cap.

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?

A single front-loaded sentence with no filler; the resource, the optional filters, and the result cap all appear before any padding. It could be tightened further, but nothing is wasted.

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?

This is a simple read-only listing tool with zero required parameters and an existing output schema, so return values need no explanation. The main omission is routing guidance against fyyd_search_podcasts, which is a modest gap for a tool this simple.

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 only 33% — just the category slug is documented. The description partly compensates by identifying lang as a language code and by implying count is bounded by the 30-result ceiling, but count itself and the slug format expectations remain unexplained.

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?

States a specific verb and resource ("Return the most popular podcasts on fyyd") plus the scope of the result set. An agent can tell this is a popularity-ranked listing rather than a keyword search, but the description never names the sibling search tool it differs from.

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?

The word "optionally" indicates the filters are not required, but there is no guidance on when to pick this over fyyd_search_podcasts, nor any exclusions or prerequisites. Usage must be inferred entirely from the tool name and siblings.

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.