Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

List categories

get_categories
Read-only

Lists Futuur event categories with their full hierarchy, enabling you to filter markets by category id or slug and browse top-level, featured, or searchable category listings.

Instructions

Lists Futuur's event categories so you can filter get_markets by category id or slug. A category belongs to a tree (for example Politics > USA > 2028 Elections); filtering by a top-level category includes everything below it. view="all" (default) is the paginated list of categories that have open events, with their full path, open event count and volume; view="root" lists just the top-level categories; view="featured" is the 10 highest-volume categories. Use get_category_details for one category's subcategories.

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

Input Schema

NameRequiredDescriptionDefault
viewNo"all" (default): paginated list of every category with open events, A to Z. "root": top-level categories only. "featured": top 10 by volume.all
limitNoCategories per page, 1 to 200. Default 100. Only with view "all".
offsetNoNumber of categories to skip, for paging. Default 0. Only with view "all".
searchNoCase-insensitive text to match in category titles. Only with view "all" or "featured".
currency_modeNoCount open events and rank volume for "play_money" or "real_money". Omit for play money counts.

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 and openWorldHint, so the description focuses on behavior: the pagination model, A-Z ordering, the fields returned per view (full path, open event count, volume), and the default play-money counting if currency_mode is omitted. The one non-obvious semantic — that filtering by a top-level category includes everything below it — is disclosed, though edge cases like empty categories are not addressed.

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-loads the purpose and why it matters, then walks through view modes in a logical order with no filler. It is on the dense side with several parenthetical asides, but every clause conveys information an agent needs to choose parameters.

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 compensates by naming the payload per view (path, open event count, volume) and the pagination behavior for the default view. An agent can pick a view, page correctly, and hand the resulting id/slug to get_markets without further information.

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 coverage is 100%, so the baseline is 3; the description still adds meaning the schema does not, specifically the hierarchy rule that a top-level category filter includes descendants, and the reason to omit currency_mode (play-money counts by default). The view modes are restated but largely mirror the schema text, so it does not earn a 5.

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 ("Lists Futuur's event categories") and immediately ties it to a downstream use (filtering get_markets by category id or slug). It also names the sibling get_category_details for the single-category case, so the boundary between the two tools is clear 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?

Explains what each view mode is for ("all" = paginated A-Z with open events, "root" = top-level only, "featured" = top 10 by volume) and routes agents to get_category_details for subcategories. It does not state an explicit exclusion such as when to skip this tool and go straight to get_markets, which keeps it short of a 5.

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