Zovo Secret Santa

Show Secret Santa status

show_secret_santa_status

Read-onlyIdempotent

Use this when the organizer asks who has opened their Secret Santa link, who added a wishlist, or wants the private links again. Takes the organizer link (it contains /m/). Returns each person's link, whether and when it was first opened, and whether they added a wishlist. Does not return who buys for whom. Does not change anything. Does not work with a person's private 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": {
      "manage_link": "<manage_link>"
    },
    "name": "show_secret_santa_status"
  }
}

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.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description still adds the authorization constraint (requires the organizer link containing /m/, not a participant link) and the scope limit on returned data. The 'Does not change anything' sentence partly restates the annotations, but the link-type requirement and the withheld assignment data are genuine additions.

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?

Front-loaded with the use case, then the input contract, then the return content, then the exclusions — a sensible ordering with no filler sentences. The '(it contains /m/)' parenthetical repeats the schema's own wording, so there is a small amount of redundant text.

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?

With an output schema present, the description only needs to characterize content and constraints, and it does: per-person links, first-opened timestamp, wishlist flag, plus explicit statements of what is omitted. Single required parameter, rich annotations, and no unanswered questions for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents manage_link's format, so the baseline is 3. The description adds meaning beyond it by telling the agent the link must be the organizer variant rather than a person's private link, which is a failure mode the schema does not mention. Minor duplication of the '/m/' hint keeps it below 5.

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?

The description opens with a specific verb+resource framing tied to the organizer's question ('who has opened their Secret Santa link, who added a wishlist, or wants the private links again') and then states exactly what it returns. The 'Does not change anything' and 'Does not return who buys for whom' lines cleanly separate it from create_secret_santa and redraw_secret_santa without needing to open a 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 three concrete trigger conditions for invocation (checking link opens, wishlist additions, re-fetching private links). It also supplies real exclusions: it will not work with a person's private link, and it does not reveal giver/recipient pairings. An agent knows both when to call it and when the call will fail or mislead.

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?