Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

Get event details

get_market_details
Read-only

Retrieve a Futuur event with full market details, including resolution rules, prices, liquidity, and status. Review the rules and current state before trading or checking an event.

Instructions

Returns one Futuur event with all its markets: the full description and resolution criteria, dates, category, volumes and liquidity, and for each market its id, title, price (probability of the long position, per currency), status, resolution, depth and last trade time. Takes an EVENT id (the id of an item from get_markets); the market ids inside the result are what get_order_book and trading tools take. Use it before trading to read the resolution rules, or to check the current state of one event.

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": "get_market_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEvent id, as returned by get_markets. Not a market id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds substantial behavioral context by enumerating what the response contains (per-currency prices as long-position probability, depth, last trade time) and how the output feeds downstream tools. It does not say what happens on an invalid or unknown id, which is the main remaining gap.

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?

Front-loaded with the action and resource, then constraints, then usage. The long enumeration of returned fields is dense but earns its place since there is no output schema. Minor cost: the first sentence is heavy with comma-separated field names.

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?

With no output schema, the description correctly carries the response shape, and it covers id semantics, downstream consumers, and use cases for a single-resource lookup tool. It stops short of error/not-found behavior, which an agent might want before relying on the call.

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?

Schema coverage is 100% and the schema already says "Event id, as returned by get_markets. Not a market id." The description mostly restates that constraint; its one genuine addition is noting that market ids inside the result are what get_order_book and trading tools take, which is about output rather than the id parameter itself. Baseline 3 is appropriate.

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 and resource ("Returns one Futuur event with all its markets") plus the exact payload contents, which clearly separates it from get_markets (listing) and get_category_details (category-level). The parenthetical contrast between event id and market id further disambiguates it from market-scoped siblings.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance ("Use it before trading to read the resolution rules, or to check the current state of one event") and, crucially, routes the agent on id provenance: the id comes from get_markets, and the market ids it returns are what get_order_book and trading tools consume. That is a concrete alternative/selection rule rather than implied usage.

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