Comedy Buff

Explore a comedian

get_comedy_comedian

Read-only

Open a comedian’s profile and specials using an ID returned by Comedy Buff tools. Shows catalog biography, artwork and their specials, including an honest empty list when none are cataloged. Continue related specials with nextOffset. Missing biography is unknown. No personal listening history, playlists or queue writes. Shows the Comedy Buff catalog; keep accompanying prose brief. Format durations in hours/minutes/seconds. Catalog totals are not verified full runtimes: never use them to rank a special as a shorter/longer listening commitment.

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": {
      "comedianId": "<comedianId>"
    },
    "name": "get_comedy_comedian"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`comedianId`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the read-only, non-destructive, open-world profile, yet the description adds real behavior: an empty specials list is returned honestly rather than erroring, a missing biography means unknown rather than absent, and catalog totals are not verified runtimes. Those are meaningful caveats an agent could not infer from the annotations.

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?

The core purpose is front-loaded, but the description accumulates several presentation directives ("keep accompanying prose brief," "Format durations in hours/minutes/seconds") that describe output styling rather than tool behavior and dilute the operational content. The runtime-ranking caveat is valuable but buried at the end.

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?

With an output schema present, return-shape explanation is unnecessary, and the description still covers the empty-result case and data-quality caveats. The main gap is pagination and limit semantics, which the prose only partially addresses.

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%, so the description carries the burden, but it only gestures at pagination with the term "nextOffset," which does not match the schema's `offset` parameter. Nothing explains `limit` (default 3, max 8) or the numeric bounds, leaving two of three parameters semantically undocumented.

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 ("Open a comedian's profile and specials") and names the return payload (biography, artwork, specials). It also distinguishes itself from the search siblings by requiring "an ID returned by Comedy Buff tools", so an agent knows this is the detail-fetch step after search_comedy_comedians.

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?

Clear about the precondition (an ID from another Comedy Buff tool) and about continuation via pagination. It also lists exclusions (no listening history, playlists, or queue writes), which steers the agent away from expecting those. It does not explicitly name a sibling to use instead for those cases, so it stops short of a 5.

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

All Comedy Buff tools Inspect

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

Need Help?