Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

Get category details

get_category_details
Read-only

Retrieve a category's title, slug, parent, full path, subcategories, open event counts, and trading volume to navigate the category tree and find events.

Instructions

Returns one category: its title, slug, parent, full path from the top-level category, whether it has subcategories and their ids and titles, how many events are open in it and its trading volume. Use it to walk down the category tree; pass a category id (or a child's id) to get_markets categories to list its events. Category ids come from get_categories or from an event's category.

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

Input Schema

NameRequiredDescriptionDefault
idYesCategory id, from get_categories or get_markets.
currency_modeNoCount open events (and children with open events) for "play_money" or "real_money". Omit for play money.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.4/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 real value beyond that by disclosing the shape of the response (subcategory presence, open event counts, trading volume), which matters because there is no output schema. It does not mention pagination, freshness of counts, or error behavior for unknown ids, so it stops short of a 5.

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?

Three tight sentences with the payload description front-loaded and the workflow/routing guidance after it; nothing is redundant. The middle field list is dense and slightly run-on, which keeps it from a 5.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so field by field. Combined with the input provenance and the tree-walking guidance, an agent has everything needed to call this correctly on the first attempt.

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 description coverage is 100%, so both `id` and `currency_mode` are already documented in the schema, including the enum values and the 'omit for play money' default. The description restates id provenance but adds nothing about `currency_mode`'s effect on the counts it advertises, so it does not meaningfully exceed the schema baseline.

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 opens with a specific verb and resource ('Returns one category') and then enumerates the returned fields (title, slug, parent, full path, subcategory ids/titles, open event count, volume). That enumeration makes it unmistakably distinct from the sibling get_categories, which returns a list rather than a single node.

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?

It states the intended workflow ('use it to walk down the category tree') and names the follow-up tool plus the exact argument to pass ('pass a category id ... to get_markets `categories` to list its events'). It also closes the loop on where inputs come from ('Category ids come from get_categories or from an event's `category`').

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