Skip to main content
Glama
Sign In

Paylo

by com.usepaylo
OverviewDiscussionsAdmin

get_wishlist

Read-onlyIdempotent

Get a public Paylo wishlist by its share link or token: items, prices, and how much funding each item still needs.

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

Input Schema

NameRequiredDescriptionDefault
urlOrTokenYesA usepaylo.com/wishlist/... share link or the bare share token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 meaningful context beyond that: only public wishlists are reachable and the response content (items, prices, per-item funding shortfall) is disclosed despite there being 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?

A single sentence that front-loads the verb and resource, then extends with scope and return content. No filler and nothing redundant.

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-only lookup with rich annotations, the description covers what is needed: the lookup key, the public-only constraint, and the shape of the result. Error behavior for invalid tokens or private wishlists is the only notable omission.

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 schema already documents the share link format. The description's 'share link or token' phrasing restates the schema rather than adding format details, so it lands at the baseline for fully-documented parameters.

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?

States a specific verb and resource (get a public Paylo wishlist), the lookup key (share link or token), and the payload (items, prices, remaining funding). No sibling tool touches wishlists, so the distinction 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?

The word 'public' implicitly scopes usage to shared wishlists, and 'by its share link or token' tells the agent how to invoke it. However, there is no explicit when-not guidance, no mention of what happens for private or expired wishlists, and no named alternative.

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

All Paylo 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