Skip to main content
Glama

Signed report

get_report
Read-onlyIdempotent

Use when a contract, a venue or a person needs the signed Tickerz print for an index: the report (ticker, period, value as a scaled integer with decimals, status provisional, final or corrected, rule version and hash, the provider reads with their snapshot hashes, settleable), its hash, the publisher's Ed25519 signature, the public recount's co-signatures, and the Solana feed account that holds it. Optional period (YYYY-MM-DD; a month as YYYY-MM-01). How to verify: https://tickerz.com/.well-known/tickerz-signer.json. Same data as GET /api/indices/{ticker}/report. Every signed print with its recount status: https://tickerz.com/signed.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoThe period, YYYY-MM-DD; newest when left out
tickerYesIndex ticker, with or without the dollar sign

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds unusual and useful context: signature verification via the well-known signer endpoint, co-signature recount semantics, and the Solana feed account holding the print.

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?

The leading 'Use when...' clause front-loads applicability, and the dense field enumeration is justified because there is no output schema. It is a single long run-on sentence, so structure could be tighter, but little is wasted.

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?

With no output schema, the description fully carries the burden of describing return values: the report fields, hash, signature, co-signatures and on-chain account. Verification URL and the equivalent REST endpoint complete the picture for an agent.

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 would be 3, but the description adds meaning beyond the schema by explaining that a month is written as YYYY-MM-01 and that omitting period yields the newest print. Ticker semantics (with or without dollar sign) come from the schema.

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?

States the specific resource (the signed Tickerz print for an index) and enumerates its contents: value, status, rule version/hash, provider reads, settleable flag, hash, Ed25519 signature, co-signatures, and Solana account. An agent can tell this apart from get_index or receipts by the signed/cryptographic framing, though no sibling is named explicitly.

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?

'Use when a contract, a venue or a person needs the signed Tickerz print' gives a clear triggering context, and it maps to a known REST endpoint. However, it offers no when-not guidance or comparison against siblings like get_index or receipts.

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