Skip to main content
Glama

Your wishlist

get_my_wishlist
Read-only

List the coins the signed-in person wants, with their notes, the revision a change needs, and an estimate of what the list costs at known market prices.

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

Input Schema

NameRequiredDescriptionDefault
yearNoOnly coins of this catalogue year.
cursorNonext_cursor of the previous page, with the same other arguments.
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, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine context beyond that — notes, a revision token a change needs, and a market-price cost estimate — but says nothing about pagination behavior, staleness of price estimates, or empty-list behavior.

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; each clause maps to real behavior. It is dense but readable, with only mild risk that cramming three output concerns into one sentence dilutes the core 'list my wishlist' message.

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 simple, read-only, zero-required-parameter tool with an output schema and full annotation coverage, the description is largely sufficient — return values need no explanation. The remaining gap is the absence of any paging hint or contrast with sibling read tools, which is minor given the schema's cursor documentation.

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% with three documented parameters (year, cursor, page_size), so the schema carries the parameter load. The description adds no semantics for the year filter or cursor chaining — the 'estimate at known market prices' clause implies price coverage limits but never states them.

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?

Names a specific verb ('List') and a well-defined resource ('the coins the signed-in person wants'), and even previews the returned fields (notes, revision, cost estimate). It reads clearly as the wishlist read tool against siblings like add_wishlist_items or remove_wishlist_item, though it never states how it differs from get_my_collection.

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: the 'signed-in person' phrasing establishes that this needs no user argument and is personal-scope. There is no explicit when-to-use, no exclusions, and no pointer to the sibling tools that mutate or read related data.

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