Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

seatgeek_get_performer

Read-onlyIdempotent

Retrieves a SeatGeek performer by ID, enabling you to look up performer details for event and ticketing workflows.

Instructions

Get a SeatGeek performer by ID.

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

Input Schema

NameRequiredDescriptionDefault
idYes
api_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is fully covered. The description adds nothing beyond the name: no error behavior on missing IDs, no rate-limit or API-key context, no note on what the performer payload contains. With annotations carrying the load, this is only minimally adequate.

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 short, front-loaded sentence with zero filler. It is efficient but arguably too thin rather than padded, so it stops short of a 5.

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

Completeness2/5

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

There is no output schema and no annotation for the return shape, and the description never says what a performer object contains or how it is keyed. With 0% schema coverage on the api_key parameter and no return-value context, an agent lacks what it needs to call this confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for 2 parameters, so the description must compensate and it does not. It only echoes the 'id' parameter in the name and says nothing about the required SeatGeek numeric ID format or what the api_key parameter is for or whether it is optional.

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 states a specific verb and resource (get a SeatGeek performer) and implies lookup semantics via 'by ID', which distinguishes it from seatgeek_search_performers. However, it never names the sibling search tool or clarifies that this is the detail-fetch counterpart, so the differentiation is only inferable.

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 guidance on when to use this versus seatgeek_search_performers or seatgeek_get_event, and no prerequisites stated. 'By ID' faintly implies you must already have an ID, but nothing tells the agent how to obtain one or what this tool returns if the ID is invalid.

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

Deploy Server

Other Tools