Skip to main content
Glama
Sign In
traivo-mcp

traivo-mcp

Official
by traivoxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Trade deep link

prepare_trade_link
Read-onlyIdempotent

Generates a Traivo link with a prefilled trade ticket so users can open, review, and sign the trade in their own wallet; it never signs or sends transactions.

Instructions

Returns a Traivo link with the trade ticket prefilled (symbol, side, amount) for the USER to open, review and sign in their own wallet. This tool never signs, sends or simulates a transaction and needs no keys. Call get_trade_quote first so the user sees price impact before opening the link.

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

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.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description confirms this by saying it never signs, sends, or simulates a transaction and needs no keys. It also explains the human-in-the-loop behavior: the USER opens, reviews, and signs in their own wallet, which annotations cannot convey.

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 sentences that front-load the return value and the safety boundary, then finish with the required call ordering. Nothing is repeated and no sentence is wasted.

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 tells the agent what comes back (a Traivo link) and what the agent should do with it. Together with the prerequisite and the no-signing guarantee, it covers everything needed to call the tool correctly for a simple three-parameter tool.

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 three parameters, including the buy/sell enum and amount semantics, are already fully documented. The mention of symbol, side, and amount confirms which fields are prefilled but adds no format or constraint detail beyond the schema, which matches the baseline of 3.

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 states a specific verb and resource: it returns a Traivo deep link with the trade ticket prefilled with symbol, side, and amount. It also names the sibling get_trade_quote as a prerequisite, so an agent can distinguish it from quoting tools without opening any 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 description gives an explicit prerequisite: call get_trade_quote first so the user sees price impact before opening the link. It also rules out signing, sending, or simulating, which tells the agent what this tool is not for. However, it does not spell out when an agent should skip this tool in favor of other flows, so it stops short of fully explicit alternatives guidance.

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