Skip to main content
Glama

mapumi Wunschzettel und Einladung

Read wish list

get_wishlist
Read-only

Read a wish list. Works with an edit link (owner view, includes edit_link) or a share link (family view). Both show which wishes are reserved and the optional name of who reserved them.

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": {
      "link": "<link>"
    },
    "name": "get_wishlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesEdit link or share link.

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 readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral value beyond that: it discloses the two link modes, that the owner view returns an edit_link, and that the response indicates which wishes are reserved plus an optional reserver name — meaningful return-content context given there is no output schema.

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?

Three compact sentences, front-loaded with the action and then the two modes and their return differences. No filler, no repetition of the tool name beyond the opening verb.

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 one-parameter read tool with no output schema, the description covers the access modes and the shape of the returned information well enough to call it correctly. Gaps are minor: no mention of invalid/expired link handling or ordering of wishes.

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% and the single parameter is already documented as 'Edit link or share link.' The description adds meaning by mapping each link type to a distinct view (owner with edit_link vs. family), but it gives no format hints, error behavior for invalid or expired links, or precedence rules. Baseline 3 is appropriate when the schema carries the parameter documentation.

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 states a specific verb and resource ('Read a wish list') and immediately clarifies the two access modes (edit link / owner view vs. share link / family view), which lets an agent understand the tool without opening the schema. It does not explicitly differentiate itself from mutation siblings such as update_wishlist, but the read-only intent is unambiguous.

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?

It tells the agent which link type produces which view, which is useful context for filling the single parameter, but it offers no when-to-use vs. when-not guidance and does not route the agent to any alternative (e.g., for creating or editing lists). Usage is implied rather than stated.

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