Skip to main content
Glama

get_stash_note

Read one saved post in full (summary, next step, transcript, permalink).

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": {
      "note_id": "<note_id>"
    },
    "name": "get_stash_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses what the response contains (summary, next step, transcript, permalink), which tells the agent this is a heavier payload than a list entry. It says nothing about permissions, whether reading marks the note as used (mark_stash_used exists as a sibling), or what happens on a missing/invalid note_id.

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?

A single front-loaded sentence with zero filler; the verb and scope come first and the return fields follow as a compact parenthetical. Nothing is redundant, though it is terse enough that it omits information the agent actually needs.

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?

With no output schema, the field enumeration in the description does real work in describing the return value, and the read-only nature of a 'read' verb is self-evident. However, for the sole required parameter the definition is silent, and there is no guidance on locating a note_id or on failure modes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the single required note_id parameter is documented nowhere. The description does not explain what a note_id is, where the agent obtains one (presumably from search_stash or recent_stash output), or its format, leaving the only parameter entirely unexplained.

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?

"Read one saved post in full" gives a specific verb (read) and a precisely scoped resource (a single saved post), and the parenthetical enumerates the returned content (summary, next step, transcript, permalink). The singular "one" implicitly contrasts with the list_/search_ siblings, but no sibling is named, so differentiation is inferred rather than stated.

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?

Usage is only implied: the agent must infer that this tool applies when it already has a note_id and needs the full body rather than a list or search result. There is no explicit when-to-use, when-not-to-use, or named alternative among search_stash, recent_stash, or list_stash_topics.

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.