Skip to main content
Glama

EX & GO marketplace

Get a live show

get_live_show
Read-only

One live show by id: status, host and co-hosts, the lots still in play, the auction running now with the current bid, and — for an ended show — the replay while it is kept. Read-only; same availability rule as list_live_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": {
      "id": "<id>"
    },
    "name": "get_live_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesshow id from list_live_shows

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description does not need to re-establish safety. It adds useful behavioral context by describing what data is included and that replay data is available only while kept, though it leaves the referenced availability rule undefined.

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?

The description is front-loaded with the core action and remains a single tight sentence. The em-dash enumeration is dense but purposeful, avoiding repetition of schema or annotation details.

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?

There is no output schema, so the description carries the burden of explaining what is returned, which it does by listing status, hosts, lots, current auction bid, and replay availability. The only notable gap is that the 'same availability rule as list_live_shows' is not defined locally for an agent unfamiliar with that sibling.

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 100%: the single id parameter is fully documented with its pattern and source tool. The description only says 'by id' and adds no format, validation, or sourcing detail beyond the schema, so baseline 3 is appropriate.

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?

The description states a specific verb and resource: retrieve one live show by id, and enumerates the returned aspects (status, hosts, lots, current auction bid, replay). This clearly distinguishes it from list_live_shows, which returns multiple shows.

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?

The phrase 'by id' implies the tool is used when a show id is already known, and it references list_live_shows for the availability rule. It does not explicitly state when not to use it or name another alternative, so it stops short of full when/when-not guidance.

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