Comedy Buff

Find comedians

search_comedy_comedians

Read-only

Find a comedian by name or keywords in their catalog biography, or browse with no query. Matches one literal, case-insensitive phrase, not semantic descriptions. Results open the Comedians grid, sorted by last name ASC (A–Z, default) or DESC (Z–A); profiles with no specials remain visible. Open a returned ID with get_comedy_comedian to see their specials. Clarify partial/contextual matches. Continue with nextOffset and the same query/sort. 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

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

Input Schema

Name	Required	Default
`sort`	No	ASC
`limit`	No
`query`	No
`offset`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare a safe, open-world read, so the description's job is added context, which it delivers: results open the Comedians grid sorted by last name, profiles with no specials remain visible, and catalog totals are unverified runtimes that must not be used to rank listening commitment. These are non-obvious behavioral facts an agent could not infer from the annotations or schema.

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 critical selection and matching information is front-loaded, which is good. However, trailing output-style rules ('keep accompanying prose brief', 'Format durations in hours/minutes/seconds') are house formatting boilerplate that does not help an agent decide whether or how to call a comedian search tool, and they dilute an otherwise dense definition.

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?

An output schema exists, so return values need not be explained, and the description covers matching semantics, sort order, zero-special visibility, pagination continuation, and the logical next call. The only real gap is the undocumented limit parameter and its cap of 8.

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 description coverage is 0%, so the description must carry parameter meaning, and it explains query (literal, case-insensitive phrase over biography text), sort (ASC = A–Z default, DESC = Z–A), and offset (pagination via nextOffset with the same query/sort). It says nothing about limit or its default of 3 and maximum of 8, leaving one of four parameters 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 (Find) and resource (comedian) plus the two modes of operation: name/keyword lookup in the catalog biography, or unfiltered browse. It is clearly distinguishable from siblings because it scopes to comedians and explicitly hands off to get_comedy_comedian for specials.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance (literal name or biography keyword, or no query at all), an explicit limitation (matches one literal case-insensitive phrase, not semantic descriptions), and a named alternative (open a returned ID with get_comedy_comedian to see their specials). It also explains how to continue paging with nextOffset and the same query/sort.

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?