Skip to main content
Glama
Sign In

JW3 MCP Server

by io.github.agnostic4321-ops
OverviewDiscussionsAdmin

Read diary day

read_diary_day
Read-only

READ-ONLY: read one diary day (trades, setups, analyses, actions) or an explicit day RANGE. Never writes — saving a note stays a propose_diary_note approval card. Pass an explicit day (YYYY-MM-DD) or an explicit start_day + end_day range (inclusive, max 31 days) — there is no today default, so ask the user when no day is given. Returns the most recent rows first with totals; quote it as observed diary state, not a live venue read.

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

Input Schema

NameRequiredDescriptionDefault
dayNoOne day in YYYY-MM-DD format (required when no range is given; no default — ask the user).
end_dayNoRange end in YYYY-MM-DD format, inclusive. Requires start_day; the range caps at 31 days.
start_dayNoRange start in YYYY-MM-DD format, inclusive. Requires end_day; the range caps at 31 days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description adds substantive behavior on top: the 31-day range cap, inclusive bounds, reverse-chronological ordering with totals, and the interpretive caveat that results are observed diary state rather than a live venue read. It also explicitly reaffirms that no write path exists here.

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 safety declaration and invocation mode are front-loaded, and no sentence is filler. It is dense — several constraints packed into one block joined by em-dashes — which costs a little scannability for an agent parsing it quickly.

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 describes return ordering and totals, and it covers the default-less requirement that could otherwise cause a malformed call. For a three-optional-parameter read tool, nothing an agent needs is missing.

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 description coverage is 100%, so the baseline is 3, and the description mostly restates the same format/inclusivity/cap rules. It still adds marginal value by framing day and start_day/end_day as mutually exclusive modes rather than three independent fields, which the schema presents without that framing.

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?

"Read one diary day (trades, setups, analyses, actions) or an explicit day RANGE" gives a specific verb, a specific resource, and enumerates the content types returned. It also separates itself from propose_diary_note by name, so an agent can choose correctly without inspecting the sibling.

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

Usage Guidelines5/5

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

It states the two invocation modes (single day, or start_day + end_day), explicitly says there is no today default and that the agent should ask the user, and names propose_diary_note as the destination for writes. Both the when and the when-not are covered.

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

All JW3 MCP Server toolsInspect
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.

Resources