Skip to main content
Glama
Sign In

Wishpile

by com.wishpile
OverviewDiscussionsAdmin

Show a wishlist in my group

get_group_wishlist
Read-only

Shows the items on a wishlist in one of the signed-in person's groups and, for someone else's list, which items are still available, which they're getting, and which someone else is getting. On their own list no claim information is shown, and in a Secret Santa only their own claims are visible. Each item has the date it was added; pass added_since to see only what's new.

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": {
      "wishlist_id": "<wishlist_id>"
    },
    "name": "get_group_wishlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
added_sinceNoOnly items added on or after this date (YYYY-MM-DD)
wishlist_idYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly and openWorld annotations, the description discloses important visibility rules: claim information is shown for someone else's list, hidden on one's own list, and restricted in a Secret Santa. It also explains what the returned items represent and how date-based filtering changes the result.

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?

The description is front-loaded with the main action and then adds the two most relevant behavioral nuances: claim visibility and date filtering. It is dense but not wasteful, and each sentence contributes useful information.

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 read-only, two-parameter tool with no output schema, the description covers the key return semantics and privacy rules an agent needs. It still does not explain where wishlist_id comes from or mention error conditions, but the core behavior is adequately documented.

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 only 50%, and the description compensates for added_since by explaining that it filters to newly added items. However, wishlist_id is not described beyond its name and the group-wishlist context, leaving part of the parameter meaning to the schema and inference.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: it shows the items on a wishlist in one of the signed-in person's groups. It also distinguishes the group/other-person view from the person's own list by explaining that own-list claim information is not shown.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the intended context clear: viewing a wishlist inside one of the signed-in person's groups, including someone else's list. It does not explicitly name alternatives such as get_my_wishlist or give when-not-to-use guidance, so it falls short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Wishpile toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources