Skip to main content
Glama

EX & GO marketplace

List live shows

list_live_shows
Read-only

Live shows (Whatnot-style video selling) on air now and coming up within a week, with host, lot count, viewers and the public link. Read-only: bidding, buying and chat happen on the site. Answers 404 while live shows are switched off or limited to a pilot the caller is not in; say the feature is not available rather than that there are no shows.

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

Input Schema

NameRequiredDescriptionDefault
qNoshow title or host name
categoryNocategory id from list_categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the readOnlyHint annotation by disclosing the 404 failure mode and its ambiguity: the tool 404s when live shows are disabled or the caller is outside a pilot, so the agent must report unavailability rather than an empty list. That is exactly the kind of non-obvious operational trait annotations cannot express.

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?

Two dense sentences with the resource and time window front-loaded, followed by the read-only boundary and the error caveat. Every clause carries operational weight; nothing is restated from the annotations or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-optional-param read tool with no output schema, the definition covers what is returned, what is out of scope, and the one failure mode that could be misread as a valid empty result. Nothing an agent needs to call or interpret this tool is missing.

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 100%, so both parameters (q for title/host text, category id sourced from list_categories) are already documented. The description adds no filtering syntax, matching behavior, or defaults beyond the schema, so the 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?

States a specific verb and resource (live shows) plus a precise scope: on air now and coming up within a week. It also enumerates the returned fields (host, lot count, viewers, public link), so an agent knows exactly what this tool yields without opening a schema.

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?

Clearly bounds when this applies (currently live or within a one-week window) and explicitly redirects interactive actions — bidding, buying, chat — to the site, which is genuine when-not guidance. It does not point to the obvious sibling get_live_show for detail on a single show, leaving that routing to inference.

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