Skip to main content
Glama

Get My Tickets

get_my_tickets
Read-only

Tickets already delivered to the caller's XP account, paged -- 'my tickets', 'pull up my seats for tonight'. Orders not yet delivered are in get_my_orders; tickets the caller is selling are in list_my_listings. Requires sign-in.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many tickets to return, 1-200. Defaults to 25.
offsetNoSkip this many. Use with limit to page.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds a genuinely useful behavioral fact beyond that: 'Requires sign-in', which tells the agent to resolve authentication before calling. It does not mention result size or empty-result behavior, but the paging note plus the output schema limit that gap.

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 core scope is front-loaded in the first clause, followed by two short routing clauses and a one-line prerequisite. Every sentence carries a distinct fact; there is no filler or restatement of the title.

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 simple two-parameter read tool with full schema coverage, annotations, and an output schema, the description covers everything needed: what it returns, how it relates to sibling tools, and the sign-in requirement. Return-value shape is correctly left to the output schema.

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%, with limit (1-200, default 25) and offset already documented in the schema. The description's 'paged' wording only signals that pagination exists, adding no syntax or format detail beyond what the schema provides, so baseline 3 applies.

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 scope and resource: tickets already delivered to the caller's XP account, returned paged. It immediately separates this from get_my_orders (undelivered) and list_my_listings (tickets being sold), so an agent can distinguish it from siblings 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 Guidelines5/5

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

Explicitly names both adjacent alternatives and the condition that selects each ('Orders not yet delivered are in get_my_orders; tickets the caller is selling are in list_my_listings'). The quoted example utterances ('my tickets', 'pull up my seats for tonight') further anchor when a user request should route here.

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