Skip to main content
Glama

Bought a wanted coin

acquire_wishlist_coin
Destructive

Record the previewed and approved purchase of a wanted coin: it becomes one purchase in the collection and leaves the wishlist.

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": {
      "intent_id": "<intent_id>"
    },
    "name": "acquire_wishlist_coin"
  }
}

Input Schema

NameRequiredDescriptionDefault
intent_idYesintent_id from prepare_moneteka_action, after the user saw its preview and agreed.

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofYes
warningsYes
request_idYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description earns credit beyond that by stating exactly what the mutation does: consumes a wishlist entry and creates a collection purchase. It also implies the authorization gate (user must have seen and agreed to a preview). It does not discuss reversibility or failure behavior, which keeps it from a 5.

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?

One sentence, front-loaded with the action and followed immediately by the two observable effects. No filler, no restatement of the title, and every clause carries 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?

An output schema exists, so return values need no explanation, and the description covers the precondition and the two side effects. What remains thin is side-effect detail such as whether the wishlist removal is reversible or what happens on a stale intent_id, but for this tool's complexity the definition is largely sufficient.

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 already carries a full description of where intent_id comes from, so the schema does the heavy lifting. The description only reinforces that the intent must be previewed and approved, adding no new format or constraint detail. Baseline 3 is appropriate for a one-parameter tool with complete schema documentation.

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 ('Record') and a specific resource ('the previewed and approved purchase of a wanted coin'), then spells out the two resulting effects: it becomes one purchase in the collection and leaves the wishlist. That distinguishes it from add_wishlist_items and remove_wishlist_item without needing to open any schema.

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 phrase 'previewed and approved' plus the schema note about intent_id from prepare_moneteka_action makes the prerequisite workflow explicit: an agent must run prepare_moneteka_action and get user agreement first. It does not name an alternative or a when-not condition, so it falls short of a 5.

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