Skip to main content
Glama
Sign In

Vectorial Data Terminal: Hyperliquid, Polymarket & yield for AI agents

by com.vectorialdata
OverviewDiscussionsAdmin

collect_prediction_winnings

Collect resolved WINNING positions into your predictions cash (Polymarket usually does this automatically at resolution; use this if get_prediction_positions shows collectable: true). Optional condition_id. Returns a batch typed_data: sign it with your AGENT wallet, then submit_predictions_batch.

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": "collect_prediction_winnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
condition_idNoCollect only this market (0x condition id); omit to collect every resolved winner

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / condition_id / description
      Added value: +"Collect only this market (0x condition id); omit to collect every resolved winner"
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Adds context the annotations cannot express: the call does not move funds by itself, it returns typed_data that must be signed with the AGENT wallet and submitted via submit_predictions_batch. That correctly signals a prepare/commit workflow despite the mutating-sounding name. It stops short of stating what happens on a stale or already-collected condition_id or whether the returned batch expires.

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?

Three compact sentences, front-loaded with the action, then the when-to-use, then the return-and-sign contract. No redundant restatement of the name or filler.

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?

For a single-optional-param prepare tool with no output schema, the description supplies everything needed to call it and act on the result: precondition, scoping option, return type, signing requirement, and the next tool. The workflow chaining is the critical missing piece for this tool and it is present.

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 the schema already explains that condition_id scopes collection to one market versus all winners. The description only restates 'Optional condition_id' without adding format or edge-case guidance, so the schema does the real work. Baseline 3 is appropriate.

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 ('Collect resolved WINNING positions into your predictions cash') and distinguishes the tool's real behavior from its name by explaining it prepares a batch rather than executing the transfer. The parenthetical that Polymarket normally handles it automatically further sharpens what this tool uniquely does.

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?

Gives an explicit trigger condition ('use this if get_prediction_positions shows collectable: true') and an explicit exclusion ('Polymarket usually does this automatically at resolution'). It also names the follow-up sibling, submit_predictions_batch, so the agent knows the sequence rather than guessing.

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

All Vectorial Data Terminal: Hyperliquid, Polymarket & yield for AI agents 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