Skip to main content
Glama

La Cartelera

One comedian

get_comedian
Read-onlyIdempotent

One comedian by slug: public profile (schema.org Person) and upcoming shows.

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": {
      "slug": "<slug>"
    },
    "name": "get_comedian"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds genuine behavioral context the annotations cannot: the response is a public profile typed as schema.org Person plus a list of upcoming shows, which tells the agent what it will receive for a simple lookup.

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?

One compact sentence, front-loaded with the resource and the lookup key, then the payload. It is a fragment rather than a sentence, but nothing is wasted and no filler precedes the essential information.

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?

For a one-parameter read tool with no output schema, the description covers the essentials: what to pass and what comes back. It stops short of covering not-found behavior or whether the upcoming-shows list is truncated or paginated, which a careful agent might still want.

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 0% for the single 'slug' parameter, so the schema supplies only the type. The description compensates partially by establishing that the slug identifies a specific comedian, but it gives no format, case sensitivity, or example, leaving the caller to guess what a valid slug looks like.

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?

The description names a specific resource ('one comedian') with a specific lookup key ('by slug') and enumerates what is returned (public profile as schema.org Person, upcoming shows). That is enough to distinguish it from get_show/get_venue, which are different entities, though it does not explicitly contrast with search or find_shows.

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 statement of when to use this versus search or find_shows, nor any prerequisite such as 'requires an exact known slug.' The only usage signal is the phrase 'by slug,' which implies the caller must already have an identifier but never says so outright.

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.

Resources