Skip to main content
Glama

Axad

Search my cards

search_bag
Read-only

Search the learner's flash cards by words in the card's language or by a short meaning. Returns the matching cards, up to limit (default 10, at most 30); lang restricts the search to one language.

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

Input Schema

NameRequiredDescriptionDefault
langNoBCP 47 code: only cards in this language.
limitNo
queryYesWords in the card's language, or a short meaning: "nunca", "double negatives".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds the result cap (default 10, at most 30) and the single-language restriction, but says nothing about result ordering, relevance ranking, or what happens when no cards match.

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 tight sentences with the search scope and result bounds front-loaded and no filler. Slight redundancy with the schema on the limit bounds keeps it from a 5.

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 read-only, three-parameter search with no output schema, the core is present: what is searched, how, and the result cap. Missing are result ordering/ranking and behavior on ambiguous or multi-language queries, which matter for a search tool returning a truncated list.

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 67%: query and lang are already documented in the schema, including the BCP 47 format and example queries. The description mostly restates those ("lang restricts the search to one language") and repeats the limit default/maximum that the schema already encodes, adding little new meaning.

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 a specific verb and resource ("Search the learner's flash cards") and explains the two query modes: words in the card's language or a short meaning. It does not differentiate itself from plausible siblings such as due_cards or browse_catalog, so it is clear but not fully self-locating.

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 implied by the query semantics (find cards by text or meaning), but there is no explicit statement of when to use this versus reviewing due cards or browsing the catalog, and no exclusions. The lang parameter's filtering intent is noted, which is helpful but not 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.