Skip to main content
Glama

Make a wish

make_wish

Tell us what you looked for with search_catalog and did not find, and what you would pay (would_pay_cents, US cents). This decides what we stock next. Also for reporting abuse or reaching us without a passport. Each call stores a new wish, never public; with a passport the answer's feedback_id lets my_feedback show our reply. Other messages: send_feedback; a purchase you used: review.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "A Markdown to PDF converter kit for Node",
      "would_pay_cents": 500
    },
    "name": "make_wish"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat you looked for, in plain words.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.
would_pay_centsNoWhat it would be worth to you, in US cents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "query": "A Markdown to PDF converter kit for Node",
      +    "would_pay_cents": 500
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Changed1 schema field changed
    • changedInput schema / properties / would_pay_cents / maximum
      Previous value: -100000New value: +1000000
  4. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
    • addedInput schema / properties / query / description
      Added value: +"What you looked for, in plain words."
    • addedInput schema / properties / would_pay_cents / description
      Added value: +"What it would be worth to you, in US cents."
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnly=false and non-idempotent; the description adds the substantive behavior: 'Each call stores a new wish, never public', which confirms the write and non-idempotent nature and discloses visibility. It further explains the downstream loop via feedback_id and my_feedback, which annotations cannot convey.

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?

The core purpose is front-loaded and every clause carries information, but the middle fragment 'Also for reporting abuse or reaching us without a passport' is structurally loose and reads as an afterthought. Dense but not padded.

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?

With no output schema, the description carries the return-value burden and does so by naming feedback_id and its use in my_feedback. Coverage of the three parameters and the mutation semantics is sufficient to call it correctly, though the phrase 'the answer's feedback_id' is slightly vague about what else the response contains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds motive beyond the schema — 'This decides what we stock next' explains why would_pay_cents matters, and 'with a passport the answer's feedback_id' clarifies what the passport_token buys you. It stops short of adding format or edge-case guidance, so not a 5.

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 action with a specific resource — record what you searched for with search_catalog and did not find, plus the price you'd pay — and explicitly delineates its neighbors ('Other messages: send_feedback; a purchase you used: review'). An agent can select this over the siblings without opening a schema.

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

Usage Guidelines5/5

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

It gives explicit when-to-use conditions (failed search on search_catalog, reporting abuse, contacting the operator without a passport) and names the alternatives for adjacent intents (send_feedback for other messages, review for used purchases). Nothing is left to inference about routing.

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.