Skip to main content
Glama
Sign In

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

by com.vectorialdata
OverviewDiscussionsAdmin

send_predictions_home

Move predictions cash back to YOUR agent wallet as native USDC (polygon, arbitrum or base; min $2) through Polymarket's bridge — the destination is always your own agent wallet. Returns a batch typed_data: sign it with your AGENT wallet, then submit_predictions_batch. Works while paused; without an API key call POST /api/agent/v1/predictions/home directly with agent_wallet.

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

Input Schema

NameRequiredDescriptionDefault
allNotrue = send all your predictions cash
to_chainNoChain where your agent wallet receives native USDC: polygon, arbitrum or base
amount_usdNoUSD of predictions cash to send (min $2)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / all / description
      Added value: +"true = send all your predictions cash"
    • addedInput schema / properties / amount_usd / description
      Added value: +"USD of predictions cash to send (min $2)"
    • addedInput schema / properties / to_chain / description
      Added value: +"Chain where your agent wallet receives native USDC: polygon, arbitrum or base"
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations declare non-readOnly, non-destructive, non-idempotent, but add nothing about mechanics; the description fills that in: the destination is hard-locked to your own agent wallet, the call returns typed_data rather than moving funds itself, signing requires the agent wallet, and it remains usable while paused. This is exactly the context an agent needs before invoking a prepare-then-submit flow.

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 core action and destination are front-loaded before the workflow and fallback details, and no sentence is filler. It is dense—three clauses packed into the opening sentence—but each carries distinct information.

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?

Despite no output schema, the description explains what comes back (a batch of typed_data), what to do with it, the minimum amount, supported chains, paused-state behavior, and the keyless HTTP alternative. Nothing material is left for the agent to infer.

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%, so `all`, `to_chain`, and `amount_usd` are already fully documented including the enum and min $2. The description restates the chain choices and the $2 floor without adding new meaning, so the baseline 3 applies.

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 ('Move predictions cash'), the exact destination ('YOUR agent wallet'), the output asset and chains ('native USDC (polygon, arbitrum or base)'), and the minimum. The 'predictions cash' framing alone separates it from send_trading_funds_home in the sibling list.

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 the follow-on workflow explicitly ('sign it with your AGENT wallet, then submit_predictions_batch') and a useful operational cue ('Works while paused') plus a fallback for keyless callers. It never names a when-not condition or a sibling alternative such as send_trading_funds_home, so it falls 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.

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