Skip to main content
Glama
Sign In

Ticker: Live Event Ticket Market

by com.findticker
OverviewDiscussionsAdmin

Get Event Research Brief

research_event

Returns the event's research brief, the one its event page shows: recent dated news coverage of the event and its performers, each item a short fact with where it was published, and no live market figures. Use it when the person asks what is happening around an event or why its market moved. A brief from the last 24 hours is served as stored. When the stored brief is older, or force is set, the call gathers a fresh one from the public web, which becomes the brief every account sees on the event page; when one cannot be gathered, the stored brief is served and fetched_at says when it was gathered. For the numbers, use get_event_analytics.

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

Input Schema

NameRequiredDescriptionDefault
forceNoGather a fresh brief even when one from the last 24 hours is stored. Quota is only consumed by a FRESH brief with findings; a stored brief and a status 'empty' result are free, and empty results are never stored, so a later call looks again. Resale-marketplace listing pages are excluded from the search: the items are coverage.
event_idYesThe event to research. Ticker event id, `ev` plus ten characters, as returned by every tool here. A marketplace event link also resolves, as does a marketplace id with its source prefix (`vs:`, `sh:`, `tm:`, `sg:`, `gt:`, `ax:`, `tp:`) or bare until 2027-09-13. An id two events share is refused with both their ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / force / description
      Previous value: -"Bypass the cache and the stale-price guard; always fetch fresh. Quota is only consumed on a FRESH result with findings; cached serves and status:'empty' results are free, and empty results are never stored, so a later call re-checks. Resale-marketplace listing pages are excluded from the search: results are coverage."New value: +"Gather a fresh brief even when one from the last 24 hours is stored. Quota is only consumed by a FRESH brief with findings; a stored brief and a status 'empty' result are free, and empty results are never stored, so a later call looks again. Resale-marketplace listing pages are excluded from the search: the items are coverage."
    • removedInput schema / properties / sources
      Removed value: -{
-  "description": "Which providers to query (e.g. ['perplexity']). Omit to query all enabled providers.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
  2. Changed1 schema field changed
    • changedInput schema / properties / event_id / description
      Previous value: -"The event to research. Ticker event id, `ev` plus ten characters, as returned by every tool here. A marketplace id also resolves when it carries its source prefix (`vs:`, `tm:`, `tp:`), and a bare marketplace id resolves until 2027-09-13."New value: +"The event to research. Ticker event id, `ev` plus ten characters, as returned by every tool here. A marketplace event link also resolves, as does a marketplace id with its source prefix (`vs:`, `sh:`, `tm:`, `sg:`, `gt:`, `ax:`, `tp:`) or bare until 2027-09-13. An id two events share is refused with both their ids."
  3. Changed1 schema field changed
    • changedInput schema / properties / force / description
      Previous value: -"Bypass the cache and the stale-price guard; always fetch fresh."New value: +"Bypass the cache and the stale-price guard; always fetch fresh. Quota is only consumed on a FRESH result with findings; cached serves and status:'empty' results are free, and empty results are never stored, so a later call re-checks. Resale-marketplace listing pages are excluded from the search: results are coverage."
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations mark this readOnlyHint=false and openWorldHint=true, and the description earns that by explaining the write path: a fresh gather 'becomes the brief every account sees on the event page,' a shared-state side effect an agent must know about. It also discloses the 24-hour staleness rule, the force override, the fallback to a stored brief when gathering fails, and the fetched_at signal that reveals which path ran.

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?

Front-loaded with what the brief is, then usage, then caching behavior, then the sibling routing — a sensible order with no filler. The middle sentence is dense and stacks several clauses (staleness threshold, force, shared visibility, failure fallback), which costs a little readability but each clause carries real operational information.

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?

There is no output schema, and the description compensates by describing the return payload (short dated facts with publication sources, no market figures) and the fetched_at field that reports gather time. For a two-parameter tool with an in-place mutation of shared account state, freshness rules, and a failure path, nothing an agent needs in order to call or interpret it is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents both parameters and the baseline is 3. The description adds value beyond it by tying force to its observable consequence — a fresh brief that overwrites what all accounts see — which the schema's force text does not make explicit, though the quota and freshness rules themselves remain in the schema rather than the description.

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 (returns the event's research brief) and immediately defines its contents: recent dated news coverage of the event and its performers, each item with where it was published, and explicitly no live market figures. It also distinguishes itself from the closest sibling by routing numbers to get_event_analytics, so an agent can tell the two apart 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 concrete triggering conditions: 'when the person asks what is happening around an event or why its market moved,' which maps directly to user intents. It also names the alternative and the exclusion boundary ('For the numbers, use get_event_analytics'), so the when-not is explicit rather than inferred.

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

All Ticker: Live Event Ticket Market toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources