Skip to main content
Glama

Recent Sales

get_recent_sales
Read-only

Recent completed sales for one event on XP: the per-ticket price and how long ago each sale cleared -- 'what did tickets actually sell for?'. An empty result means no verified sales in the window. Asking prices over time are in get_price_history. event_id comes from search_events or search_market.

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": {
      "event_id": "<event_id>"
    },
    "name": "get_recent_sales"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesEvent identifier from search_market or search_events.

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 the safety profile is covered. The description adds genuinely new behavior: results are limited to completed, verified sales in a window, and an empty response is a meaningful negative answer rather than an error. It doesn't discuss window size or pagination limits, which keeps it from a 5.

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?

Front-loads the resource and return fields, then handles the disambiguation and provenance in short trailing clauses with no filler. The quoted intent phrase does real routing work rather than padding.

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 single-parameter read tool with an output schema and full annotation coverage, nothing material is missing: scope, return semantics, empty-result meaning, sibling routing and ID provenance are all present. The output schema is left to describe the exact response shape, which is correct.

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?

Only one parameter with 100% schema description coverage, so the schema already carries the meaning. The description's note that event_id comes from search_events or search_market largely restates the schema's own description, adding no syntax or constraint detail beyond it. 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+resource ("Recent completed sales for one event") and even enumerates the returned fields (per-ticket price, time since sale cleared). It explicitly separates itself from get_price_history by naming that sibling as the asking-price tool, so an agent can choose 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?

Gives an intent framing ("what did tickets actually sell for?"), names the alternative for asking prices over time, and explains where event_id comes from (search_events or search_market). It also states what an empty result means, which resolves the main ambiguity an agent would hit when calling it.

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