Skip to main content
Glama

Tickerz

by com.tickerz
OverviewDiscussionsAdmin

Receipts

receipts
Read-onlyIdempotent

Use when someone asks how past attention spikes turned out, or wants a track record they can check, losses included. Closed events, newest first, each with its 24h, 7d and 30d receipts (forward return, or null until due; benchmark is BTC for crypto and SPY for stocks, with benchmark_ret_pct over the same window), score_at_open, peak_score and the driver with its source. Each event carries symbol (the same ticker as assets.symbol). Each proofs row carries proof_url, the proof as JSON, an absolute link in the same form as an index first_print.proof_url. A receipt is due 24 hours, 7 days and 30 days after the event opened, so the newest page has null 30d receipts until they are due: page back to events old enough for them with before and before_id: each page carries next_before (its last event's opened_at, exactly as stored) and next_before_id (that event's id), null when there is nothing older. Send both back and the next page starts right after that event, including events opened at the same time. before alone (any ISO time) reads events opened strictly before that time, so on its own it can skip events opened at exactly that time. Optional symbol filter, applied in the query, so limit counts only that ticker's events and an empty page means none older on record. Same store as GET /api/receipts. peak_heat is the deprecated alias of peak_score, same value, kept until at least 2026-12-31.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo1 to 100, default 30
beforeNoOptional cursor: only events opened before this time (ISO 8601, e.g. 2026-09-01T00:00:00Z). Send next_before from a page, with before_id, for the page before it; without before_id, events opened at exactly this time are skipped
symbolNoOptional ticker to filter, e.g. BTC
before_idNoOptional, with before: next_before_id from a page. The next page starts right after that event, so events opened at the same time are not skipped

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / before
      Added value: +{
+  "description": "Optional cursor: only events opened before this time (ISO 8601, e.g. 2026-09-01T00:00:00Z). Send next_before from a page, with before_id, for the page before it; without before_id, events opened at exactly this time are skipped",
+  "type": "string"
+}
    • addedInput schema / properties / before_id
      Added value: +{
+  "description": "Optional, with before: next_before_id from a page. The next page starts right after that event, so events opened at the same time are not skipped",
+  "type": "string"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, idempotent, closed-world. The description adds value beyond that: receipts become null until due, cursor semantics via next_before/next_before_id, and a deprecation horizon (peak_heat until 2026-12-31). Strong added context despite annotations doing the safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph mixing return-shape details, cursor semantics, filter behavior, deprecation notes, and cross-endpoint references. Front-loaded usage is good, but the wall of clauses about null receipts and cursor edge cases is hard to parse; it should be broken into bullets or short sections.

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

Completeness4/5

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

No output schema, yet the description enumerates the return fields (receipts, benchmark, score_at_open, peak_score, driver, proof_url, next_before/next_before_id, peak_heat alias) and cursor contract, so an agent can consume the response. Would reach 5 with clearer field/key naming for the proofs rows.

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 baseline is 3. The description goes further, explaining interaction between 'before' and 'before_id' (skip vs. include same-time events) and clarifying that 'symbol' filters in the query so 'limit' counts only that ticker. Adds real semantic value on top of the schema.

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: closes events with their receipts, newest first. Distinguishes from siblings like arena, base_rate, board by describing a concrete track-record surface with named fields. An agent can tell what this returns without opening anything.

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?

Opens with an explicit when-to-use trigger ('Use when someone asks how past attention spikes turned out, or wants a track record they can check, losses included') and mentions 'Same store as GET /api/receipts'. Does not name an alternative sibling to use instead, so it falls short of 5.

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

All Tickerz 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