Zovo Secret Santa

Redraw Secret Santa

redraw_secret_santa

Destructive

Use this when the organizer wants a new random draw for an existing Secret Santa, for example because they saw an assignment by mistake. Takes the organizer link. Works only while nobody has opened a private link; it replaces the old draw with the same rules, keeps the same private links and keeps wishlists. Does not add or remove people (make a new Secret Santa for that).

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": {
      "manage_link": "<manage_link>"
    },
    "name": "redraw_secret_santa"
  }
}

Input Schema

Name	Required	Description	Default
`manage_link`	Yes	The private organizer link from when the draw was made, e.g. https://secret-santa.zovo.one/m/AbC.../XyZ... (it contains /m/).

Output Schema

Name	Required	Description	Default
`event`	Yes
`rules`	Yes
`budget`	Yes
`closed`	Yes
`people`	Yes
`warnings`	Yes
`manageUrl`	Yes
`publicUrl`	Yes
`can_redraw`	Yes
`expires_on`	Yes
`opened_count`	Yes
`exchange_date`	Yes
`wishlist_count`	Yes
`participant_count`	Yes
`people_count_shown`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds the information an agent actually needs before calling: the draw is replaced wholesale under the same rules, existing private links and wishlists are preserved, and the operation is blocked once any participant has opened a private link. These side effects and invariants go well beyond the annotation flags.

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?

Front-loaded with the usage trigger, then precondition, then side effects, then scope exclusion — each sentence carries distinct decision-relevant content. No filler or repetition of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A destructive, non-idempotent mutation with one parameter and an output schema; the description covers the precondition, what is preserved, what is replaced, and what is out of scope. Return values need not be explained given the output schema, so nothing an agent needs to call it correctly is missing.

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 is fully documented in the schema, including format and the /m/ marker. The description's 'Takes the organizer link' merely restates it, adding no new meaning. Baseline 3 applies.

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+resource ('a new random draw for an existing Secret Santa') and immediately bounds it against siblings with 'Does not add or remove people (make a new Secret Santa for that).' An agent can distinguish this from create_secret_santa and show_secret_santa_status without opening 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 Guidelines5/5

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

Gives an explicit trigger ('when the organizer wants a new random draw... because they saw an assignment by mistake'), an explicit hard precondition ('Works only while nobody has opened a private link'), and an explicit redirect to a different tool for roster changes. When-to-use, when-not, and alternative are all present.

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

All Zovo Secret Santa 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?