Skip to main content
Glama

Read text

stash_get
Read-only

Read the text saved at a path. Returns an error if nothing is there.

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": {
      "path": "<path>"
    },
    "name": "stash_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath like myproject/notes: 1-256 chars of a-z 0-9 _ - with / between parts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact: it returns an error if nothing is stored at the path. That partially offsets the odd idempotentHint=false, which the description does nothing to explain; an agent cannot tell whether a repeated read might fail because the entry was consumed or removed.

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 short sentences, front-loaded with the action and followed by the failure mode, with zero padding or repetition.

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?

A single-parameter read whose safety profile and parameter format are fully covered by annotations and schema. The only real omission is the return type; the description says 'the text' but does not confirm the response shape, which matters slightly given there is no output schema.

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?

With 100% schema description coverage on the single path parameter, the schema already supplies the syntax and constraints. 'At a path' adds no new meaning beyond what the schema declares.

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?

States a concrete verb and resource: 'Read the text saved at a path.' That is clearly distinct from stash_put and stash_delete in the sibling list, though the description never names an alternative and leaves the differentiation implicit.

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

Usage Guidelines2/5

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

Provides no guidance on when to use this versus stash_put, or when to avoid it. The only contextual hint is the error behavior for empty paths, which is about outcome rather than selection.

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.

Resources