Skip to main content
Glama
Sign In

Profullstack

by com.profullstack
OverviewDiscussionsAdmin

p0dcasters: List shows by subject, language or domain

p0dcasters_list_shows
Read-onlyIdempotent

[p0dcasters] Shows in one category (a single lowercase word such as history or comedy), one language (ISO 639-1 code) or on one domain, ranked by catalogue depth and longevity weighted by recency, the same order as the site's pages. Call browse first for the categories and languages that exist and how many shows each holds.

Served by p0dcasters (https://p0dcasters.com/mcp).

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": "p0dcasters_list_shows"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoA domain, e.g. example.org.
limitNoDefault 30.
offsetNo
categoryNo
languageNoISO 639-1, e.g. en, de, pt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior beyond them: the result ordering ('ranked by catalogue depth and longevity weighted by recency, the same order as the site's pages'), which tells the agent results are not alphabetical or relevance-scored. It does not describe result record contents or pagination totals.

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?

Two front-loaded sentences with the scoping and ranking before the prerequisite pointer; little waste. The ranking clause is dense but conveys ordering semantics that would otherwise be unknown, and the trailing server URL line is boilerplate.

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?

With five optional parameters and no output schema, the definition covers selection and ordering but not what a returned show contains or whether pagination yields a total. It is adequate to call the tool correctly in the common case but leaves the caller guessing about combined filters and result shape.

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?

Schema coverage is 60% and 'category' has no schema description at all, but the description supplies its format ('a single lowercase word such as history or comedy'), which the schema omits. It also frames host as 'one domain' and language as ISO 639-1, matching the schema. It leaves open whether category, language and host may be combined or are mutually exclusive, which matters for correct invocation.

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 ('Shows in one category... one language... or on one domain') plus the ranking rule, which no other sibling exposes in that form. It also distinguishes itself from p0dcasters_browse by naming that tool as the prerequisite for discovering which categories and languages exist.

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 an explicit routing instruction: 'Call browse first for the categories and languages that exist and how many shows each holds,' which establishes when this tool is the wrong first call. It does not address when to prefer p0dcasters_search or what to do when no filter matches, so guidance is clear but not exhaustive.

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

All Profullstack toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources