Skip to main content
Glama

list_stash_mentions

Books, movies, shows, podcasts, places, or people named across every saved post, not just one. Use for 'what books/movies have I saved', regardless of what those posts were mainly about.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_stash_mentions"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOne of book, movie, show, podcast, place, product, person, other. Omit for all.
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose one non-obvious trait: mentions are extracted even from posts whose main topic is something else. However, it says nothing about ordering, pagination, how many mentions come back, or what a result entry looks like, leaving meaningful gaps for a read tool.

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?

Two short sentences, both earning their place, with the scope constraint ('not just one') front-loaded. The opening is a fragment without a verb, which is slightly awkward but does not waste space or bury the key information.

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?

For a simple two-optional-parameter read tool with no output schema and no annotations, the description covers purpose and when-to-use adequately. It does not explain the undocumented limit parameter or hint at the shape of returned mentions, which are the remaining gaps an agent would need filled.

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 coverage is 50%. The description's enumeration of kinds (books, movies, shows, podcasts, places, people) reinforces the documented 'kind' parameter, though it omits 'product' and 'other' and never says kind acts as a filter. The 'limit' parameter is undocumented in both schema and description, so the description only partially compensates.

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?

The description names the specific resource (books, movies, shows, podcasts, places, people mentioned inside saved posts) and the scope ('across every saved post, not just one'), which distinguishes it from single-note siblings like get_stash_note. It lacks an explicit verb ('list'), but the resource and scope are concrete enough that an agent can tell what it returns.

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 gives an explicit trigger phrase — "Use for 'what books/movies have I saved'" — plus a clarifying condition ('regardless of what those posts were mainly about'). It does not name a competing sibling or state when not to use it, so it stops short of full routing guidance.

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.