Skip to main content
Glama

paper_trade_log

Read-only

Tradelog $0.01: scored paper ledger JSON. Paid GET is HTTP 422 if the CSV is missing, unreadable, malformed, or older than 7 days. Price $0.01 (10000 atomic USDC on Base). Pays via x402.

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

Input Schema

NameRequiredDescriptionDefault
setupNoSetup name. Optional. Case-insensitive exact match.
sinceNoISO-8601 timestamp. Optional. Filters on entry_time_et (inclusive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds important behavior beyond those: the call costs $0.01 via x402 on Base, and paid GET returns HTTP 422 when the CSV is missing, unreadable, malformed, or older than 7 days. That payment and failure-mode detail is valuable and does not contradict the read-only annotation.

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 description is three short sentences and front-loads the resource and price. There is little waste, though the $0.01 price is repeated and the opening phrase 'Tradelog $0.01: scored paper ledger JSON' is cryptic rather than informative.

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

Completeness3/5

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

For a simple two-parameter read tool, the description covers payment and stale-data failure conditions well. However, with no output schema, it should explain what the ledger JSON contains and what 'scored' means; currently an agent knows the cost and error behavior but not the return content.

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%, and the schema already explains that setup is an optional case-insensitive exact match and since is an optional ISO-8601 filter on entry_time_et. The description adds no additional meaning about these parameters, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a paid GET returning a paper ledger as JSON, so the resource and read nature are somewhat clear. However, 'Tradelog' and 'scored paper ledger JSON' are idiosyncratic and never plainly state that this retrieves paper trading log entries. It also does not distinguish itself from siblings such as trade_signals or live_grade.

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 gives pricing and failure conditions but no guidance on when to use this tool versus alternatives. It does not mention the optional setup or since filters as selection criteria, nor does it say when not to use it.

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