Highwire

Get trade tape

get_trade_tape

Read-onlyIdempotent

Retrieve the live higher.fun trade tape to track recent buys, sells, launches, and graduations across the platform in real time.

Instructions

The live feed across all of higher.fun: the latest buys, sells, launches and graduations.

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_trade_tape"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds that the feed is 'live' and spans the whole platform, which is genuine context, but it says nothing about how many entries are returned, whether it is a snapshot or incremental stream, or how often to poll.

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?

A single front-loaded sentence with no filler. Scope ('across all of higher.fun') comes before the enumeration of event types, so the agent gets the most important framing first.

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

Completeness3/5

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

With no output schema and no parameters, the description carries the burden of explaining the return value, and it only partly does so by naming the four event types. It omits anything about result size, ordering, or refresh cadence, which are the details an agent needs to use a live feed correctly.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add and the schema is fully trivially covered. Baseline 4 applies for a no-argument tool.

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?

The description names the resource and its scope concretely: a live feed 'across all of higher.fun' containing 'buys, sells, launches and graduations'. That implicitly separates it from per-coin siblings like get_coin_trades, though the distinction is never stated outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is for platform-wide recent activity rather than a single coin, and the word 'live' suggests real-time polling. No explicit when-to-use, when-not-to-use, or named alternative (e.g. get_coin_trades, list_coins) is given.

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