The Doll Scout · Collecting Tools

prepare_swap_event_card

Read-onlyIdempotent

Prepare a user-supplied collector event template or personal preparation card, with explicit wanted/offered names, source matches, Markdown and a reviewable share link. Supports participant swaps, store-only swaps or display-only rules. Does not verify the organizer, event, ownership, matches or trades. The link contains readable user-supplied data: anyone holding it can read, edit or forward it. Review before sharing; expired cards are read-only. No browser storage access or automatic publication.

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": {
      "kind": "<kind>",
      "eventName": "<eventName>",
      "eventDate": "<eventDate>",
      "exchangeMode": "<exchangeMode>"
    },
    "name": "prepare_swap_event_card"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	Yes
`note`	No
`wanted`	No	Explicit names only, preferably Series title / figure name. Unknown names remain unresolved; no inferred trade intent.
`offered`	No	Only items explicitly offered; prohibited in display-only mode. Repeated names do not establish quantities.
`language`	No	Interface language; some browser-only tools are available only in EN/DE.	en
`rulesUrl`	No	Optional user-supplied HTTPS rules link; not fetched or verified.
`eventDate`	Yes	Calendar date YYYY-MM-DD as supplied for the event; no attendance or timing verification.
`eventName`	Yes
`exchangeMode`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the annotations, the description discloses critical behavioral traits: the share link contains readable user-supplied data that anyone can read, edit or forward; expired cards become read-only; there is no browser storage access or automatic publication; and no verification of organizer, event, ownership, matches or trades occurs. These are exactly the safety and side-effect details an agent needs for a link-generating tool.

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 description is front-loaded with the tool's purpose and then layers safety warnings, with every sentence carrying useful information. It is dense but not bloated; slight gains could come from separating the caveats into clearer clauses, but nothing is wasted.

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?

Given nine parameters and no output schema, the description does a good job covering purpose, modes, verification limits, data exposure, expiry and publication behavior. It leaves some gaps around the exact output structure (e.g., Markdown content, source matches) and the role of a few parameters, preventing a perfect score.

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 description coverage is 56%, and the description adds some meaning by mapping 'template or personal preparation card' to the event/card kind and the three exchange modes to peer/store/display. However, it does not explain the 'note', 'language' or 'rulesUrl' parameters, and 'source matches' is mentioned without a corresponding parameter explanation. Baseline 3 is appropriate given partial schema coverage.

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?

The description states a specific verb and resource: 'Prepare a user-supplied collector event template or personal preparation card,' and enumerates the resulting artifacts (wanted/offered names, source matches, Markdown, share link). This clearly distinguishes it from sibling calculators and guides, though it does not explicitly name a sibling alternative.

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?

It gives clear usage contexts ('Supports participant swaps, store-only swaps or display-only rules') and explicitly states what it does not do ('Does not verify the organizer, event, ownership, matches or trades'). It does not reference specific sibling tools as alternatives, but the mode guidance effectively frames when to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All The Doll Scout · Collecting Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?