Skip to main content
Glama

simulate_trade

Calculate a paper-trade estimate from the latest Coinbase Exchange spot price. This never places, signs, or submits an order and excludes fees and slippage.

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": {
      "product": "<product>",
      "side": "<side>",
      "amount": "<amount>",
      "amount_unit": "<amount_unit>"
    },
    "name": "simulate_trade"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYes
amountYesFor quote sizing, a USD amount. For base sizing, an amount of the crypto asset.
productYes
amount_unitYesWhether amount is USD or units of the crypto asset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does well by stating that it never places, signs, or submits an order and that fees and slippage are excluded. It could add more about price freshness, authentication, or output details, but the key safety profile is disclosed.

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?

The description is two tightly written sentences with zero waste. The core purpose and critical safety constraint are front-loaded.

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?

For a simulation tool with no annotations and no output schema, the description covers the essential behavior: it estimates from spot price, does not execute orders, and excludes fees and slippage. It could say more about the returned estimate, but the critical invocation and safety context is present.

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 50%, and the schema itself clarifies the ambiguous parameters amount and amount_unit while side and product use self-explanatory enums. The description adds no parameter-level meaning beyond the schema, so a 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 gives a specific verb and resource: calculate a paper-trade estimate from the latest Coinbase Exchange spot price. It is clearly distinct from real order placement, but it does not explicitly differentiate itself from sibling tools like get_crypto_prices or get_market_snapshot.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'paper-trade estimate,' and the safety note clarifies what the tool will not do. However, there is no explicit guidance on when to choose this tool over the sibling price/snapshot tools.

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