Skip to main content
Glama

search_stash

Search the user's saved social-media posts by keyword or by meaning (describe it loosely: 'that hotel room under the sea'). Use at the START of any work task (coding, design, agents, automations, writing, client or session planning, research), before proposing an approach. Returns compact hits; call get_stash_note(id) for the full note.

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": {
      "query": "<query>"
    },
    "name": "search_stash"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 5.
queryYesConcept words, tool names, or the underlying problem, not the task as typed. Try a second query if the first is weak.
statusNo"unused" for things never acted on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden, and it does disclose the return shape ('compact hits') and the follow-up path for full content. It implicitly scopes results to the user's own saved posts. It does not mention auth, rate limits, or what fields a hit contains, which keeps it short of a 5.

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, zero waste: the what and the dual-mode note come first, then the when-to-use trigger, then the follow-up pointer. The parenthetical example earns its place by clarifying the semantic search style.

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?

For a 3-param read tool with no annotations and no output schema, the definition covers purpose, timing, query strategy, and next step. The one gap is that 'compact hits' is never unpacked — with no output schema, a hint at what a hit contains would fully close the loop.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning about the query parameter's style — loosely described concepts, illustrated with 'that hotel room under the sea' — and advises a second query attempt. The limit and status parameters are left entirely to the schema.

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 and resource ('Search the user's saved social-media posts') and distinguishes two retrieval modes, keyword vs. semantic ('describe it loosely'). An agent can immediately tell this is a semantic lookup over saved posts, distinct from get_stash_note or recent_stash.

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

Usage Guidelines5/5

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

Gives explicit timing ('Use at the START of any work task... before proposing an approach') and enumerates task contexts where it applies. It also routes to the alternative explicitly: 'call get_stash_note(id) for the full note', plus retry strategy ('Try a second query if the first is weak').

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.