Skip to main content
Glama

Register a created prediction market

register_prediction_market
Idempotent

Lists a newly created market on indexfy.xyz under its sector. Call with the createMarket transaction hash once mined, within 1 hour.

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": {
      "txHash": "<txHash>",
      "sector": "<sector>"
    },
    "name": "register_prediction_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorYes
txHashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already mark it as a non-read-only, open-world, idempotent write against an external site. The description adds value beyond that by naming the external destination (indexfy.xyz) and disclosing a hard 1-hour submission window from the transaction having been mined. It still doesn't say what happens on expiry or on duplicate registration, despite idempotentHint=true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero padding. The action and destination come first, and the timing constraint follows immediately as the operative condition for the caller.

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?

For a two-parameter registration call with a full annotation set and no output schema, the description covers the essential mechanics: where the market lands, which hash to supply, and the deadline. Failure modes and any confirmation/link returned are the only notable omissions.

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 0%, so the description carries the burden, and it does clarify that txHash must be the createMarket transaction hash (not an arbitrary hash) and that sector is the index/classification the market is listed under. The enum values themselves are only in the schema, and format expectations for the hash are left to the regex pattern.

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?

States a specific verb and resource: it registers ('lists') a newly created market on indexfy.xyz under a sector. This is clearly distinguished from the build_* siblings that construct transactions, since this operates on the already-mined createMarket hash. It doesn't explicitly name a sibling, so it stops short of a 5.

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?

Gives a concrete precondition and trigger: call after the createMarket transaction is mined, and within 1 hour. That is clear when-to-use context, but it doesn't say what to do if the window has passed or how it relates to get_prediction_market / list_prediction_markets for verification.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources