Skip to main content
Glama

Your collection

get_my_collection
Read-only

List the signed-in person's own coins or their individual purchases, with the collection totals. view=lots returns each purchase with the lot_id and revision that a correction or removal of it needs.

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

Input Schema

NameRequiredDescriptionDefault
viewNocoins = one row per owned coin with the total quantity; lots = every individual purchase with its lot_id and revision, which a change or removal needs.coins
yearNoOnly coins of this catalogue year.
cursorNonext_cursor of the previous page, with the same other arguments.
coin_idNoOnly this coin (coin_id from search_coins).
page_sizeNoRows per page.

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofYes
warningsYes
request_idYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful scoping ('signed-in person's own') and notes that lots carry the identifiers a downstream correction or removal requires. The 'with the collection totals' detail is largely restating what the output schema documents, and pagination behavior is left unmentioned.

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 tightly written sentences with the primary scope front-loaded and the view=lots semantics second. Little waste, though 'with the collection totals' overlaps with the output schema and could be trimmed.

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?

With annotations, a full-coverage input schema, and an output schema, the essential context for correct invocation is present. The remaining gap is routing: it gestures at 'a correction or removal' without naming update_collection_lot or remove_collection_lot, so an agent must infer the connection.

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%, so every parameter, including the view enum and its two values, is already documented in the schema. The description reinforces the practical purpose of view=lots but adds no syntax, format, or constraint details beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource: lists the signed-in person's own coins or their individual purchases, plus collection totals. It also distinguishes the two modes (aggregated rows vs. per-purchase rows). It does not explicitly differentiate itself from siblings like get_collection_analytics or get_my_wishlist, so it falls short of a 5.

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 description implies when each view is appropriate by tying view=lots to the lot_id and revision needed for a correction or removal. However, it never states when to use this tool rather than get_collection_analytics or get_coin_details, and it does not name the mutation siblings that consume lot_id/revision.

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