Skip to main content
Glama

Foresea Forecasting

by ink.foresea
OverviewDiscussionsAdmin

foresea_polymarket_meta

Call this to fetch Polymarket metadata: event series listings, community discussion comments for a market, or sports league metadata (target: 'series', 'comments', 'sports', 'teams').

    'series' lists the series and how many events each holds, not the events
    themselves -- fetch a series by slug for those. 'sports' lists every league
    with the ids that link it to other tools, not league artwork or homepages.
    'comments' gives the comment, its author address and its reaction count,
    not the commenters' profiles or individual reactions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoseries
market_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It transparently explains the scope of each target, including what data is intentionally omitted. This gives the agent a strong sense of the tool's behavior, though it does not cover edge cases like missing market_id or invalid targets.

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?

The description is front-loaded with the main purpose and target list, then organized into target-specific clarifications. Every sentence adds useful information, though the format is slightly longer than necessary because it repeats the target names in the explanatory lines.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has two parameters and an output schema, but with no parameter documentation and no annotations, the description needs to cover invocation details more fully. It explains three modes well but leaves 'teams' undefined and never clarifies when market_id should be supplied, especially for 'comments'.

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 0%, so the description must compensate. It explains valid target values and their meanings, but it never names or explains the market_id parameter, and the 'teams' target is listed without any detail. The description partially bridges the gap but leaves key parameter semantics ambiguous.

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 states a specific action ('fetch Polymarket metadata') and precisely identifies the resource types handled: series listings, comments, sports leagues, and teams. It also differentiates what the tool does not return, making its purpose unmistakable even among many sibling tools.

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?

The description gives clear context for when to call the tool by enumerating the four target modes and what each returns. It does not explicitly name alternative sibling tools or say 'use X instead', but it does provide useful exclusion boundaries such as 'not the events themselves' and 'not commenters' profiles'.

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

All Foresea Forecasting 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