Skip to main content
Glama
Sign In
stealthguard-402

stealthguard-402

by ak10082247-max
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

alpha_polymarket_whale_orderflow

Track smart-money whale orders, detect CLOB orderbook imbalances, and surface Limitless/Polymarket cross-venue arbitrage spreads above a configured minimum order size.

Instructions

Deep CLOB orderbook imbalance, smart-money wallet tracking, and Limitless/Polymarket cross-venue arbitrage spread matrix. Price: 0.02 USDC on Base.

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

Input Schema

NameRequiredDescriptionDefault
min_order_usdNoMinimum order size in USD
include_cross_venueNoInclude cross-venue arbitrage matrix

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the price and chain (0.02 USDC on Base), but it does not state whether the tool only reads data, what permissions or payment flow are required, how fresh the data is, or what the response contains.

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 dense sentences with no filler: the analytical capabilities come first and the price/chain note second. Every phrase contributes information.

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

Completeness2/5

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

For a composite analytics tool with no annotations and no output schema, the description is thin. It lists data domains and cost but says nothing about return structure, coverage, limitations, or data freshness, leaving the agent under-informed about what to expect.

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 100%, and both parameters are fully documented in the schema. The description does not add syntax, defaults, or interpretation beyond the schema, so the baseline score of 3 is appropriate.

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?

The description names specific domains — CLOB orderbook imbalance, smart-money wallet tracking, and Limitless/Polymarket cross-venue arbitrage spreads — so the agent can infer the tool's analytical purpose. However, it does not explicitly distinguish itself from related siblings such as polymarket_top_whales or polymarket_alpha_divergence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives no guidance on when to use this tool versus alternatives, nor any preconditions or exclusions. The pricing line adds commercial context but does not help an agent choose between this and related Polymarket tools.

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

Deploy Server

Other Tools