wren

Get a Wren note

get_note

Read-onlyIdempotent

Show one note's title, subject, page size and its pages (number, id, ink stroke count, whether Wren can add ink to it). Use it to pick a page to replace (write_notebook_page target.pageNumber) or draw onto (draw_figure).

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": {
      "noteId": "<noteId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "get_note"
  }
}

Input Schema

Name	Required	Description
`noteId`	Yes	The note's id, from list_notes or a previous Wren result.
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`note`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered and the description does not need to restate it. What the description adds beyond structured data is the per-page capability flag (whether Wren can add ink), which tells the agent this call is a precondition check before a write. Return format is not explained, but an output schema exists, so that is not a gap.

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?

Two sentences with no filler. The output inventory comes first, then the actionable purpose, so the agent reads the capability before the routing advice. Nothing is repeated from the annotations or schema.

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 a rich output schema, complete annotations, and full parameter documentation, the description covers the remaining burden: what the note detail contains and why an agent would fetch it. The only thin spot is that the relationship to list_notes (how noteId is obtained when it is not already known) is not stated, but that is minor given the schema note.

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%, including detailed guidance on noteId, context, llm_model, and conversation_id, so the schema already does the heavy lifting and baseline 3 applies. The description adds only that noteId comes from list_notes or a previous Wren result is not restated, and it does link the returned page number to write_notebook_page's target.pageNumber, a small but genuine semantic bridge.

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?

The description opens with a specific verb and resource ("Show one note") and enumerates exactly what is returned: title, subject, page size, and per-page number, id, ink stroke count, and write capability. That level of detail distinguishes it cleanly from list_notes, which is implied to return multiple notes at a shallower level.

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?

It states the downstream use explicitly and names the two sibling tools it feeds: write_notebook_page (with the target.pageNumber parameter spelled out) and draw_figure. That is clear routing guidance with concrete parameter linkage. It stops short of stating when not to use it (e.g., for scanning many notes, where list_notes would be appropriate), so it does not reach the explicit when/when-not bar of a 5.

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

All wren 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.

Resources

Need Help?