Skip to main content
Glama
Sign In

tech-risk

by io.github.rezearcher
OverviewDiscussionsAdmin

gate_swap_preview

FREE live sample of the gate_swap pre-trade GO/HOLD/BLOCK decision for a demo Base token (usdc|weth|cbbtc|aero|degen), same shape as the paid gate_swap tool. The paid gate_swap tool additionally returns a top-level sized_verdict one-liner plus the full sizing object (entry/exit slippage simulation + round-trip breakeven + max_safe_notional_usd); the paid_adds block here names those fields. No payment required.

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

Input Schema

NameRequiredDescriptionDefault
sideNodefault buy
tokenNodemo token, default usdc
notional_usdNotrade size in USD (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 and does well: it discloses the zero-cost nature, the demo-only token scope, that results are live rather than cached, and which fields the paid tool adds plus the paid_adds block. It does not mention rate limits, freshness guarantees, or what a BLOCK verdict means operationally.

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 key differentiator (free sample, no payment) and the scope (demo tokens) are front-loaded, and each subsequent clause adds a distinct fact about the paid tier. Slightly dense with backticked field names, but nothing is redundant.

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

Completeness4/5

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

No output schema exists, so the description must convey return shape, which it does by asserting the output mirrors gate_swap and naming the withheld paid fields via paid_adds. It stops short of describing the actual verdict fields, leaving the agent dependent on knowledge of the sibling tool's output.

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%, with enums and defaults already documented for side, token, and notional_usd, so baseline is 3. The description only reinforces that the token must be a demo Base token, adding no syntax, units, or interpretation beyond the schema.

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+resource: a GO/HOLD/BLOCK pre-trade decision for a demo Base token, and explicitly distinguishes it from the sibling gate_swap by calling itself the free sample of it. An agent can tell exactly which tool to reach for without opening either schema.

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 free-vs-paid framing ('FREE live sample... No payment required', paid adds sizing) gives clear context for choosing this over gate_swap, and the demo-token whitelist bounds its use. It never states an explicit exclusion such as 'do not use for real position sizing', leaving that inference to the agent.

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

All tech-risk 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