outs-mcp

Paper trades

get_trades

Read-onlyIdempotent

Retrieve paper trades newest first, including entry, exit or open P&L, and net return after fees and price impact. Filter by open/closed status, agent, and limit to review strategy performance.

Instructions

Paper trades, newest first: entry, exit (time, mcap, reason) or open P&L, and the net return after costs (fees on both sides, price impact, network fee).

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

Input Schema

Name	Required	Description
`open`	No	true: open trades only; false: closed trades only
`agent`	No	Agent key from get_agents: a wallet address, house-<name>, or strat-<id> for a strategy
`limit`	No	How many trades, 1-50 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description adds genuinely useful context beyond that — sort order and what the net return nets out (fees both sides, price impact, network fee) — but says nothing about pagination costs beyond the 50 cap or freshness of the data.

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?

A single dense sentence that front-loads the resource and ordering before the return shape. With no output schema, every clause (entry, exit fields, cost breakdown) carries real informational load, so nothing is wasted.

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?

With no output schema, the description does the necessary work of enumerating return components, and the 100%-covered schema handles inputs. What's missing is whether results are paged beyond the limit cap or how recently trades are computed, a minor gap.

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 schema already documents open, agent, and limit fully; the description adds the 'open P&L' framing that makes the open flag's semantics intuitive. Baseline 3 is exceeded slightly, though no new parameter detail is introduced.

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?

Names a specific resource (paper trades) and states the ordering (newest first) plus the returned fields, which is more than a tautology. It stops short of distinguishing itself from siblings like get_live_calls or get_performance, so an agent must infer the paper-vs-live distinction.

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

Usage Guidelines2/5

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

The description offers no when-to-use or when-not guidance and names no alternative tool. Nothing tells the agent to pick get_trades over get_live_calls or get_performance; only the schema's open/agent parameters hint at filtering intent.

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

Deploy Server