Hopi

Secret Santa generator

hopi_secret_santa_generator

Read-onlyIdempotent

Draw Secret Santa gift pairings from a list of names. Every person gives to exactly one other person, and nobody is assigned to themselves (a derangement). Returns the giver to receiver pairs. Source: https://hopi.co.uk/secret-santa-generator/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`names`	Yes	The list of participant names (at least two, no duplicates)

Output Schema

TableJSON Schema

Name	Required	Description
`pairs`	No
`summary`	Yes
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026
- addedOutput schema / required
```
Added value: +[
+  "source_url",
+  "summary"
+]
```
First observedSep 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds behavioral substance beyond that: the assignment guarantees (every giver gives to exactly one other person, no self-assignment) and the giver-to-receiver pair format. It does not explicitly say the assignment is random, but 'Draw' and the source context imply it.

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 compact and front-loaded, with the purpose in the first sentence and constraints right after. The trailing source URL is not needed for tool invocation, which keeps it from a perfect score, but it is a minor blemish.

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?

For a single-parameter read-only tool with a full input schema, annotations, and an output schema, the description is complete: it covers purpose, constraints, return pairs, and provenance. Nothing essential is missing for an agent to select and call it correctly.

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?

The single 'names' parameter is already fully described in the schema (array, minItems 2, no duplicates). The description only refers to 'a list of names' and adds no parameter-level details, so the baseline of 3 for full schema coverage 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?

The description names a precise action and object: 'Draw Secret Santa gift pairings from a list of names.' It goes beyond the title by specifying the derangement constraint (no self-assignment, one recipient per giver), which clearly distinguishes it from other generator siblings like random_team_generator.

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?

Clear intended context is stated: use when you need Secret Santa pairings from a list of names. There are no explicit when-not-to-use instructions or named alternatives, but no sibling tool offers the same pairing logic, so the omission is minor.

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

All Hopi 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?