Skip to main content
Glama

Get a show

get_show

Retrieve a show by its UUID and include its setlist when available, so you can inspect performance details and song order.

Instructions

Get one show by id, plus its setlist when one exists.

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": {
      "show_id": "<show_id>"
    },
    "name": "get_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
show_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses one real behavioral trait — that the setlist is included only "when one exists" — which is valued non-obvious context, but it says nothing about permissions, behavior for an unknown id, or error cases.

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 sentence with zero waste, front-loading the core action and appending only the one genuinely extra fact (conditional setlist inclusion).

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 lookup with no output schema, the description covers what is returned (the show, plus its setlist when present), which is the key missing structured information. It is slightly thin on failure/empty behavior but otherwise complete.

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?

There is one parameter with 0% schema description coverage, so the description should compensate. "By id" clarifies that show_id identifies a single show, but adds no format or constraint detail beyond what the schema's uuid type already conveys.

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 gives a specific verb and resource ("Get one show by id") and implies single-record scope, which implicitly contrasts with the list_shows sibling. It does not explicitly name or differentiate itself from siblings like get_setlist or list_shows, so it falls short of a 5.

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?

Usage is only implied: fetch a single show when you already have its id. There is no explicit statement of when to prefer this over list_shows or get_setlist, and no prerequisites or exclusions are mentioned.

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