Skip to main content
Glama

Add to the wishlist

add_wishlist_items

Add the previewed and approved coins to the wishlist; coins already owned or wanted are reported, not added.

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

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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the write/no-destroy profile is covered structurally. The description adds real value by disclosing that already-owned or already-wanted coins are reported rather than added, implying a non-failing, partially-skipping outcome. It does not describe any auth or rate-limit behavior, and the output schema carries the result shape.

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 front-loaded sentence with a semicolon clause, each half carrying distinct information (what is added, what is skipped). No filler or redundant restatement of the title.

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 mutation with annotations and an output schema, the description supplies the prerequisite and the dedup/skip behavior an agent needs before calling. Only edge behavior on failures is unaddressed, and that is reasonably left to the output schema.

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?

Only one parameter, and the schema already documents intent_id at 100% coverage including its origin in prepare_moneteka_action. The description's 'previewed and approved' phrasing reinforces that requirement but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

Specific verb (add) plus resource (wishlist) plus the scope of what may be added ('the previewed and approved coins'). It does not name a sibling such as acquire_wishlist_coin to differentiate, but an agent can still tell what the tool does from the sentence alone.

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?

States the precondition that coins must have been previewed and approved, which routes the agent to prepare_moneteka_action first. It gives no explicit when-not guidance or named alternative, so it stops 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources