Skip to main content
Glama

mark_stash_used

Mark a save as acted on. Call it when you actually used a note. It is the only signal that separates a knowledge base from a graveyard.

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

Input Schema

NameRequiredDescriptionDefault
note_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/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 never states whether marking is idempotent, what happens with an unknown note_id, whether it is reversible, or whether it requires ownership of the note; the third sentence is motivational framing rather than behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The action is front-loaded in the first sentence, which is good, but "It is the only signal that separates a knowledge base from a graveyard" is rhetorical padding that conveys no operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A mutation tool with no annotations, no output schema, and an undocumented required parameter is missing the essentials: what state change occurs, what is returned, and what identifies the target note. Relative to its complexity, the description leaves too much unspecified.

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?

The single required parameter note_id has 0% schema description coverage, and the description never mentions the identifier or its expected format. An agent must guess whether this is a stash note ID, a mention ID, or an external URL reference.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb and object ("Mark a save as acted on"), but the vocabulary shifts between "save," "note," and the stash terminology used by its siblings, so the agent must infer that a "save" is a stash note. The core action is recognizable but not precisely scoped.

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?

"Call it when you actually used a note" gives a usable trigger condition, which is more than most mutation tools offer. However, it names no alternatives or exclusions, so there is no guidance on what to do when a note was merely read or partially relevant.

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.