Keel — Hyperliquid trading strategies

Read Strategy Notes

keel_strategy_notes_read

Read-onlyIdempotent

Read the saved notes for a Hyperliquid trading strategy to recover durable context like prior change reasons, baseline metrics, and known risks.

Instructions

Read the notes saved on one of the caller's strategies — the durable context that outlives one session; adding one is keel_strategy_notes_add. The result carries notes: the most recent limit notes (default 10), newest first, each with its text, author and time — why prior changes were made, baseline metrics, known risks.

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": {
      "strategy_id": "<strategy_id>"
    },
    "name": "keel_strategy_notes_read"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum notes to return, newest first (1-100).
`strategy_id`	Yes	Strategy id whose notes to read.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.9.0Oct 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine context beyond that: what a note contains (why changes were made, baseline metrics, known risks), the default limit, and newest-first ordering.

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?

Front-loads the verb, resource and scope in the first clause before the alternative and result details. It is dense but every clause carries information; no filler sentences.

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 an output schema present, the description needn't spell out return values, yet it still sketches the result shape (text, author, time). Combined with the sibling reference and scope, an agent has enough to call it correctly.

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 both parameters are already documented. The description restates the default (10) and newest-first ordering of `limit`, which is largely redundant with the schema, so the baseline 3 applies.

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?

States a specific verb (read) and resource (notes saved on the caller's strategies), scoped to 'one of the caller's strategies.' It explicitly names the sibling keel_strategy_notes_add for the write counterpart, so the agent can distinguish it from alternatives without opening the schema.

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

Usage Guidelines4/5

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

Names the alternative ('adding one is keel_strategy_notes_add') and frames the purpose as durable cross-session context, which clearly implies when to reach for it. It stops short of explicit when-not conditions, but the routing to the sibling is clear.

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

Deploy Server