Skip to main content
Glama

mapumi Wunschzettel und Einladung

Add wishes

add_wishes

Add one or more wishes to a list. Needs the edit link.

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": {
      "edit_link": "<edit_link>",
      "wishes": "<wishes>"
    },
    "name": "add_wishes"
  }
}

Input Schema

NameRequiredDescriptionDefault
wishesYes
edit_linkYesThe secret edit link (https://wunschzettel.mapumi.de/b/…) or just its key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / wishes / items / properties / image_url
      Added value: +{
      +  "description": "Optional direct URL of the main product picture (https://…jpg/png/webp), e.g. the og:image of the product page if you have seen it. Used when the picture cannot be fetched from the page, many shops block our server. Empty string removes it.",
      +  "maxLength": 1000,
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is supplied. The description adds the authentication prerequisite (secret edit link), which is valuable, but says nothing about the non-idempotent consequence of repeated adds, partial failures in a batch, or what happens to items whose links are blocked by shops.

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?

Two short sentences with the prerequisite front-loaded after the action; no filler. Slightly terse for a mutation tool, but 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?

With no output schema, the description never indicates what is returned (created wish IDs, the updated list) or how batch errors surface, and it omits any dedup/conflict behavior. For a write tool with a 100-item array, that leaves the agent guessing about results, though the core call is callable as written.

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 50% and the nested wish fields already carry rich descriptions (link, text, price, favorite, image_url), so the schema does most of the work. The description only adds that the edit link is required and that wishes may be one or many; it contributes little meaning beyond the schema.

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?

'Add one or more wishes to a list' gives a specific verb and resource and conveys the batch nature (1..100), which separates it from update_wish/remove_wish by name and action. It stops short of explicitly contrasting with the sibling updater, but an agent can select it without opening the schema.

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?

'Needs the edit link' states a hard prerequisite, which is genuinely useful for a write tool. However, there is no guidance on when to add a new wish versus calling update_wish (e.g., whether adding duplicates is allowed) and no mention of what the edit link must be in terms of permissions.

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