Skip to main content
Glama
Sign In

Annalist

by io.github.ryanroskowski
OverviewDiscussionsAdmin

One outcome market with a week of prices

outcomes_market
Read-only

One Hyperliquid outcome (prediction) market by id: readable title, structured details (teams, thresholds, deadlines, official source), each side's implied probability, 24h change, volume and outstanding value, its question, and a week of hourly prices per side. Ids come from /v1/outcomes/list. Signed. Not investment advice. Price: $0.01 USDC per call via x402 (Base or Solana).

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": {
      "id": "<id>"
    },
    "name": "outcomes_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses material invocation context: the response is signed, it costs $0.01 USDC per call via x402 (payable on Base or Solana), and it explicitly carries a not-investment-advice disclaimer. Payment and signing requirements are exactly the behavioral facts an agent must know before calling.

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 purpose and returned fields are front-loaded in the first sentence, followed by short, high-value sentences on id sourcing, signing, disclaimer, and price. The field enumeration is long but each item is informative, and nothing is padded.

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 carries the return-value burden and does so thoroughly (title, structured details, implied probability, 24h change, volume, outstanding value, question, a week of hourly prices per side). Combined with payment and id-sourcing details, an agent has everything needed to call it correctly.

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

Parameters3/5

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

With only one parameter and 0% schema description coverage, the description must compensate. It says the market is fetched 'by id' and that valid ids come from /v1/outcomes/list, which is genuinely useful, but it does not restate the numeric format (the schema's pattern) or give any example id.

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?

The description states a specific verb+resource: fetch one Hyperliquid outcome (prediction) market by id, and enumerates what comes back. It is clearly the singular counterpart to outcomes_list, so an agent can distinguish the two without opening either schema.

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?

It gives the prerequisite context — 'Ids come from /v1/outcomes/list' — which tells the agent to call the list tool first. There is no explicit when-not or alternative scenario, but the usage path is unambiguous for a by-id lookup.

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

All Annalist toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources