Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official
by Coinversaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

HIP-4 Outcomes

hip4_outcomes
Read-onlyIdempotent

List active HIP-4 outcome contracts traded recently, with IDs, fills, unique wallets, notional USDH, and timestamps to identify active prediction markets.

Instructions

List active HIP-4 outcome contracts that traded recently. Returns outcome IDs, question metadata when available, side tokens, fills, unique wallets, notional USDH, and first/last traded timestamps. Use when users ask what prediction/outcome markets are active. Outcomes are sorted by notionalUsdh descending and capped at limit (default 25, max 200; the API route has no paging, so the cap is applied by the connector) — the response carries count (returned), totalCount, truncated and a note; raise limit or shorten hours to see more. HIP-4 fills are indexed from mainnet launch (2026-05-02; the API clamps every look-back to it) — see data_coverage for freshness.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hoursNoLook-back window in hours. Default 24, max 168.
limitNoMax outcomes to return, largest notionalUsdh first (default 25, max 200).
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.0
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 25,
+  "description": "Max outcomes to return, largest notionalUsdh first (default 25, max 200).",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
  2. Addedv0.7.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/no-destructive, and the description layers on substantial extra behavior: sort order (notionalUsdh descending), the connector-side cap because the API route has no paging, the count/totalCount/truncated/note fields, how to see more (raise limit or shorten hours), and the mainnet-launch indexing floor with a pointer to data_coverage.

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?

Purpose is front-loaded in the first sentence, and the following clauses each carry real information (sort order, cap mechanics, index floor). It is dense and slightly long, but no sentence is filler.

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 still enumerates the return payload (IDs, question metadata, side tokens, fills, wallets, notional USDH, timestamps, truncation fields) and the look-back constraint. An agent has everything needed to call it and interpret truncation.

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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining why the caps exist (connector-applied, no paging) and the operational consequence of truncated/count, which materially clarifies how limit and hours behave.

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 opens with a specific verb+resource: 'List active HIP-4 outcome contracts that traded recently,' and even enumerates the returned fields. It is clear what the tool does, though it never explicitly distinguishes itself from near-neighbors like hip4_most_active or hip4_outcome_summary, so sibling differentiation is left to inference.

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 users ask what prediction/outcome markets are active' gives a concrete trigger context, and 'see data_coverage for freshness' routes the agent elsewhere for a related concern. There are no explicit when-not conditions or named alternatives for overlapping tools such as hip4_most_active.

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

Deploy Server

Other Tools