Skip to main content
Glama
Sign In

Fivebar Trading

by io.github.fivebar-xyz
OverviewDiscussionsAdmin

One prediction market and its history (Polymarket)

prediction_market
Read-only

One Polymarket market or event by its polymarket.com link, slug or market id: the Yes odds now, 24-hour and weekly change, spread, liquidity, volume, end date, the resolution rules, and the odds over the last day, week or month. For an event with several markets (like each Fed meeting), lists them all and charts the busiest unless the link names one. Read-only.

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": {
      "market": "<market>"
    },
    "name": "prediction_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketYespolymarket.com/event/... link, an event or market slug, or a market id
intervalNoHistory window, default 1w

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 'Read-only' sentence is largely redundant, but the description adds real behavior beyond them: the exact data returned (Yes odds, 24h/weekly change, spread, liquidity, volume, end date, resolution rules) and how multi-market events are resolved.

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 resource and accepted identifiers, then the returned fields, then the multi-market branch. It is a dense run-on sentence with a redundant 'Read-only' tail, but every other clause conveys information.

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 carries the return-value burden and does so by enumerating the market metrics and history windows. Ambiguity around multi-market events is also addressed, leaving little an agent would need but not know before calling it.

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 both parameters are documented there, including the interval enum and default. The description only adds a little interpretation ('unless the link names one' for event links), which is helpful but not substantial param guidance.

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 concrete verb and resource ('One Polymarket market or event by its polymarket.com link, slug or market id') and enumerates the returned fields, so an agent can tell this single-market lookup apart from the plural listing sibling prediction_markets without opening a 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?

Gives usable context: use a link/slug/id for a specific market, and for a multi-market event it lists all markets and charts the busiest unless the link names one. It doesn't explicitly name prediction_markets as the browse alternative, so the when-not is implied rather than stated.

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

All Fivebar Trading toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources