Skip to main content
Glama

La Cartelera

One show

get_show
Read-onlyIdempotent

One show by slug, as the schema.org ComedyEvent its public page publishes (date, venue, lineup, offer).

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_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world access, so the safety profile is covered. The description adds genuinely new behavioral information in saying the record is rendered as the schema.org ComedyEvent its public page publishes, with the exposed fields (date, venue, lineup, offer) listed — valuable because no output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that identifies the retrieval key, the resource, and the return shape with zero filler. Nothing could be removed without losing 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 this is nearly sufficient: it names the lookup key and describes the returned entity and its fields, compensating for the absent output schema. The only real gap is behavior for an invalid or missing slug.

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 coverage is 0% and slug is only typed as a string, so the description must carry the load. Saying 'by slug' and 'its public page publishes' hints that the slug is the public-page identifier, but it gives no format, case, or not-found behavior for the parameter.

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 (get one show), narrows retrieval to a single item by slug, and names the return type as a schema.org ComedyEvent. That cleanly separates it from find_shows and the other get_* siblings, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

'One show by slug' implies the precondition (you already have a slug) and the contrast with a search tool, but there is no explicit when-to-use/when-not statement, no mention of what to do when the slug is unknown, and no pointer to find_shows for discovery.

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