Skip to main content
Glama

mapumi Wunschzettel und Einladung

Create wish list

create_wishlist

Create a new wish list for a child, optionally with first wishes. Returns edit_link (secret, for parents) and share_link (for family).

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

Input Schema

NameRequiredDescriptionDefault
dateNoDate of the occasion as YYYY-MM-DD (optional).
wishesNo
messageNoOptional message from the parents to everyone giving gifts, shown above the wishes. Line breaks are kept. Empty string removes it.
occasionNoFree text, any culture or religion, e.g. "Geburtstag", "Weihnachten", "Eid al-Fitr", "Diwali".
child_nameNoFirst name of the child (optional).

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

A3.6/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write, and the description adds genuinely new context: the response carries edit_link (secret, for parents) and share_link (for family), which is the only place the return shape is documented since no output schema exists. It still says nothing about permissions, failure modes, or what happens if creation is repeated.

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?

Two sentences, front-loaded with the action, then the return contract. No filler, no restatement of the title, and every clause carries information an agent needs.

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 5-parameter, all-optional creation tool with no output schema, the description covers purpose and return values well, and the schema covers parameter details. It lacks guidance on when creation is the right choice versus adding wishes to an existing list, which is the remaining gap.

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 80% and the schema already documents date, wishes, message, occasion and child_name in detail, including optionality. The description adds only the notion that the call can seed "first wishes" at creation time, which is already implied by the wishes array; 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?

States a specific verb and resource ("Create a new wish list") plus scope ("for a child, optionally with first wishes"), which clearly separates it from get_wishlist, update_wishlist and delete_wishlist. It stops short of explicitly naming a sibling or contrasting behavior, so it lands at a strong 4 rather than a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as add_wishes or update_wishlist. The phrase "optionally with first wishes" faintly hints that wishes can also be added later, but the agent is left to infer it.

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