Dayze — Life Context

Get Trades

get_trades

Read-only

The user's broker fills and trade journal notes from synced accounts, newest first: days back (default 30, max 90), symbol, limit (default 40, max 100). Read only: Dayze cannot place, change or cancel an order. ($0.05; API key required)

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
`days`	No	Days back to include (default 30, max 90), e.g. 30.
`limit`	No	Maximum rows to return, e.g. 20.
`symbol`	No	Ticker symbol, e.g. AAPL.

Output Schema

Name	Required	Description	Default
`count`	Yes
`fills`	No
`notes`	No
`notes_unavailable`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 9, 2026
- addedInput schema / properties / days / description
```
Added value: +"Days back to include (default 30, max 90), e.g. 30."
```
- addedInput schema / properties / limit / description
```
Added value: +"Maximum rows to return, e.g. 20."
```
- addedInput schema / properties / symbol / description
```
Added value: +"Ticker symbol, e.g. AAPL."
```
AddedNov 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the annotations, the description adds ordering (newest first), default and maximum values, cost ($0.05), and API-key requirements. These are meaningful operational details, though it does not discuss pagination behavior or response shape beyond what the output schema likely covers.

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 compact and front-loaded, with the core resource and ordering stated first. Every element, including the cost and API-key note, adds useful context without unnecessary wording.

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?

Given the annotations, full schema coverage, and an output schema, the description supplies the remaining operational context an agent needs: read-only scope, ordering, limits, cost, and authentication. Nothing critical appears missing for correct invocation.

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 documents all three parameters. The description repeats the defaults and maxima for days and limit but adds little semantic meaning beyond the schema itself.

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 states a specific resource and scope: broker fills and trade journal notes from synced accounts, returned newest first. It is clear what the tool returns, but it does not explicitly distinguish itself from sibling tools or name alternatives.

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?

It gives useful usage boundaries such as read-only behavior and the fact that Dayze cannot place, change, or cancel orders. However, it does not say when to use this tool versus alternatives or provide explicit exclusions beyond the read-only constraint.

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

All Dayze — Life Context tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.