Skip to main content
Glama

search_saved

Read-onlyIdempotent

Keyword search over saved items. Example: query="standing desk", limit=10.

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_saved"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 20
queryYesSearch text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default: 20)"New value: +"Max results, default 20"
    • changedInput schema / properties / query / description
      Previous value: -"Search query"New value: +"Search text"
  2. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds no behavior beyond that – nothing on matching semantics (substring vs token), case sensitivity, result ordering, or what an empty result means. Only an illustrative invocation is provided.

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 with the purpose front-loaded and no filler. The example sentence is low-value relative to the space it takes, but nothing is verbose or buried.

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-parameter read tool with full schema coverage and complete annotations, the description is adequate to call it correctly. However, there is no output schema, and the description says nothing about the shape of results or match behavior, leaving an agent to discover those at call time.

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 100%, so query (search text, max 500) and limit (max results, default 20, range 1-50) are already documented in the schema. The example shows query="standing desk", limit=10, which illustrates usage but adds no semantic meaning; the example limit of 10 also differs from the documented default of 20, which could momentarily mislead.

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?

"Keyword search over saved items" states a specific verb (search), resource (saved items), and retrieval mode (keyword), which separates it from get_item, get_wishlist, and list_collections. It stops short of naming a sibling, so it is clear but not fully differentiated.

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 by "keyword search" – an agent can infer it should be used when it has text to match rather than an ID. There is no statement about when to prefer get_item or get_wishlist instead, and no exclusion guidance for exact-ID lookups.

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