Skip to main content
Glama

Search MemoStem cards

search_card_browser
Read-onlyIdempotent

Search or page through active approved cards without reopening the browser.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
cursorNo

Output Schema

NameRequiredDescriptionDefault
resultsYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds genuinely new scope information: results are limited to "active approved" cards, and the tool supports paging. It does not explain what the cursor means on expiry or how paging terminates, but with annotations carrying the safety burden a 3 is fair.

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?

A single front-loaded sentence with no filler; the search/paging duality and the browser-avoidance rationale are both packed in efficiently. The browser clause is slightly oblique, costing a point on precision rather than length.

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?

An output schema exists and annotations are rich, so return format and safety do not need description coverage. Still, for a search tool the description leaves query semantics (empty string default behavior) and cursor lifecycle unaddressed, which an agent would need to call it confidently.

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 description coverage is 0% for both parameters, so the schema contributes nothing beyond types and defaults. The description partially compensates by mapping "search" to the query parameter and "page through" to the cursor parameter, but it never states whether an empty query returns everything, how matching works, or how to obtain an initial cursor.

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 specific verb pair ("search or page through") and a scoped resource ("active approved cards"), which tells the agent this is a read/list operation over an approved subset rather than the full card set. The trailing clause "without reopening the browser" implicitly contrasts it with the browser-opening sibling, but it never names that sibling explicitly.

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?

The phrase "without reopening the browser" implies the tool is preferred when the browser is already open or should not be disturbed, which is a usable selection cue. However, there is no explicit when-not guidance and no named alternative such as browse_memostem_cards, so the agent must infer the routing decision.

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.