Skip to main content
Glama

Ego Agent Marketplace

Trade Check (paid, 0.01 USDC)

trade_check
Idempotent

PAID tool, run by Ego Agent. Before a trade on Arc: is this pool safe to trade in right now, how far would this amount move the price, and how much may one trade carry. Measured from the pool on chain at the moment of the call. Payment is x402 over MCP in USDC on Arc: call it without a payment to be told the price and where to pay; call it again with the signed payment in _meta["x402/payment"] to get the answer. You are charged only when the answer is delivered.

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>",
      "usdc": "<usdc>"
    },
    "name": "trade_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideNobuy = USDC to the token (default), sell = the token to USDC.
usdcYesThe size of the trade, in USDC.
marketYesThe token traded against USDC: BTC, ETH or EURC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The description adds substantial behavior beyond the annotations: the tool is paid (0.01 USDC via x402), requires a signature round-trip, and results reflect the pool state at call time. Annotations declare openWorldHint/idempotentHint/non-destructive, and the description is consistent with a live data read that nonetheless moves funds, so readOnlyHint=false is not contradicted. It stops short of describing response shape or what happens on a failed/underpaid attempt.

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?

Cost and paid status are front-loaded, followed by purpose and then payment mechanics — a sensible ordering with no filler. The payment explanation runs long and leans on a dense em-dash clause, but every sentence carries operational information the agent needs.

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?

With no output schema, the description still conveys what the call returns — a safety verdict, a price-impact estimate, and a size ceiling — plus the payment handshake required to obtain it. For a three-parameter, read-oriented paid check, nothing essential to correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description reframes the inputs in intent terms: 'this amount' maps usdc to a price-impact calculation, and 'how much may one trade carry' signals the max-size output. That gives an agent a reason to pick values rather than just the type constraints the schema already supplies.

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 names a specific resource and scope: a pre-trade check on an Arc pool answering three concrete questions (pool safety now, price impact of a given amount, maximum size one trade may carry). It states the measurement is taken from the on-chain pool at call time, which further pins down what the tool actually does. The sibling tools (get_service, search_services) are service-discovery tools, so no ambiguity exists.

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?

It gives explicit timing guidance — 'Before a trade on Arc' — and spells out the two-step invocation protocol: first call without payment to learn the price and payee, then call again with the signed payment in _meta["x402/payment"]. It also states the billing condition ('charged only when the answer is delivered'), which governs when the agent should expect a charge.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources