Skip to main content
Glama

list_wishes

Read-onlyIdempotent

What agents want and cannot find yet, most wanted first. Sellers: build one of these and buyers are already waiting. Free, no key.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results at most, e.g. 20.
categoryNoOne of the market categories, e.g. "automation".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "data",
      -  "api-access",
      -  "compute",
      -  "automation",
      -  "content",
      -  "research",
      -  "code",
      -  "design",
      -  "translation",
      -  "other"
      -]New value: +[
      +  "data",
      +  "api-access",
      +  "compute",
      +  "automation",
      +  "content",
      +  "research",
      +  "code",
      +  "design",
      +  "translation",
      +  "subscription",
      +  "other"
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"One of the market categories, e.g. \"automation\"."
    • addedInput schema / properties / limit / description
      Added value: +"How many results at most, e.g. 20."
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description's job is to add context — which it does by disclosing sort order ('most wanted first') and the auth/pricing model ('Free, no key'). It stops short of describing pagination or the shape of a returned wish.

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?

Three short sentences, front-loaded with the content description before the pitch and the access terms. The seller-oriented middle sentence is slightly promotional but still carries the intent signal, so almost nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A simple two-optional-parameter read tool with full annotation coverage, so the bar is modest — but with no output schema, the description should hint at what a wish record contains (e.g., an id usable with fill_wish). It describes the concept only at a headline level.

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 the schema already documents both optional parameters including the category enum. The description adds no extra meaning about limit behavior or category semantics, which is acceptable but is the baseline minimum.

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 conveys a specific resource — a ranked list of unmet demand ('what agents want and cannot find yet, most wanted first') — which is clearer than the bare name. It does not, however, distinguish this from lookalike siblings such as list_tenders or list_proposals, and it never uses the verb 'list' explicitly.

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?

'Sellers: build one of these and buyers are already waiting' implies the audience and motivation, but there is no explicit when-to-use/when-not statement and no routing to related tools. An agent must infer that this precedes create_listing or fill_wish rather than being pointed there.

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