Skip to main content
Glama
Sign In
traivo-mcp

traivo-mcp

Official
by traivoxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Trade quote

get_trade_quote
Read-onlyIdempotent

Get a live, read-only Uniswap V3 quote for swapping a token against USDC on Ethereum, including amounts, average price, price impact, premium, impact ladder, and pool fee.

Instructions

Live pre-trade quote for swapping a token against USDC on Uniswap V3 on Ethereum mainnet, read from the chain at the current block. Returns amount in/out, average price at this size, price impact vs a small trade, premium vs the reference (the listed share price for tokenized stocks, Chainlink ETH/USD for ETH, the Hyperliquid mid for other crypto it lists), an impact ladder at larger sizes and the pool fee. Ethereum gas is not included. Read-only: nothing is signed or sent.

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": {
      "symbol": "<symbol>",
      "side": "<side>",
      "amount": "<amount>"
    },
    "name": "get_trade_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYesbuy = spend USDC for the token; sell = sell the token for USDC.
amountYesSize of the trade: USDC to spend for a buy, number of tokens for a sell.
symbolYesTicker as Traivo lists it, e.g. NVDA, TSLA, SPY, ETH, WBTC. Case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/destructive/idempotent, but the description adds genuinely new behavior: the quote is read on-chain at the current block, Ethereum gas is excluded, and the 'premium' benchmark differs by asset class (listed share price, Chainlink ETH/USD, Hyperliquid mid). It also restates the safety profile ('nothing is signed or sent'), which is redundant but harmless.

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?

Front-loaded with the core purpose, then the return contents, then the safety note — a sensible order. It is dense, with a stacked parenthetical defining three different premium benchmarks, but no sentence is filler and the length is justified by the amount of return information it must carry.

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 carries the return-value burden and does so explicitly: amount in/out, average price, price impact vs a small trade, premium vs reference, impact ladder at larger sizes, pool fee, and the exclusion of gas. For a three-parameter quoting tool this leaves nothing material an agent would need before calling it.

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%, so the schema already defines side, amount and symbol including the buy/sell USDC convention. The description only indirectly reinforces semantics via 'average price at this size' and 'impact at larger sizes'; it adds no per-parameter syntax or format detail beyond the schema, 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 (live pre-trade quote) plus the exact venue, chain and pair convention (swap a token against USDC on Uniswap V3, Ethereum mainnet). This distinguishes it from siblings such as prepare_trade_link, which presumably constructs the actual trade, without needing to open 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 phrase 'pre-trade quote' and 'live ... read from the chain at the current block' make the usage context clear: this is a sizing/preview step, not an execution step. However, it never explicitly says when not to use it or names prepare_trade_link as the follow-on, so the routing is implied rather than spelled out.

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