Skip to main content
Glama

Search my collection

search_my_collection
Read-onlyIdempotent

Find cards in your SlabLineage collection by name, set or card number. Returns up to 25 items with quantity, condition and SL Consensus value.

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

Input Schema

NameRequiredDescriptionDefault
queryYesCard name, set name or card number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that by disclosing the 25-item return cap and the fields returned (quantity, condition, SL Consensus value), which the annotations do not convey. It does not say whether matching is exact or fuzzy, which is a minor residual gap.

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 filler: the first establishes what is searched and how, the second establishes the return shape and limit. Front-loaded with the action and resource, with the result contract following immediately.

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 single-parameter read tool with no output schema, the description covers the essentials: what is searched, how it is matched, how many results come back, and what fields they carry. The only meaningful omissions are pagination behavior past 25 items and match strictness.

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 100% and the single query parameter is already documented as "Card name, set name or card number." The description restates the same matching modes without adding syntax, format examples, or behavior for ambiguous or partial matches, so the schema is doing the semantic work.

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?

"Find cards in your SlabLineage collection" gives a specific verb plus a clearly scoped resource (the user's own collection, not the general catalog), which distinguishes it from a sibling like search_cards. It stops short of naming the alternative explicitly, so differentiation is implied by the possessive scope rather than stated.

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 "in your ... collection" implies the use case is looking up owned inventory, which is enough to infer when to reach for this over a catalog search. There is no explicit when-to-use or when-not-to-use statement, no mention of the summary sibling, and no guidance on what to do when the 25-result cap is hit.

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