Print name tags and place cards for an event from a guest list: adhesive name badges, 8 per sheet.
Score is being calculated.
Use this when the user wants printable name tags, name badges, a name tag template, place cards or table tent cards for a list of people. Send the whole guest list in guests (array of names or objects, pasted lines, or CSV text with first, last, company, table); everything else is optional: event name, sort (as given, last name, first name, table), style (classic, bold, minimal), accent colour, paper (US Letter 5395 badges or A4). Returns a name badge PDF (8 per sheet) and a folded tent place card PDF (2 per page) plus a preview. Does not make address labels, business cards, seating charts or wristbands.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Order: as_given (default), last_name, first_name or table. Example: last_name. | |
| event | No | Event name printed small on each badge and place card, e.g. Spring Gala 2026. | |
| paper | No | letter (default: 5395-size badges, 8 per sheet) or a4 (generic 90 x 60 mm badges, 8 per sheet). | |
| style | No | Badge style: classic (event name and a rule, default), bold (colour header band) or minimal (name only, event small at the bottom). | |
| accent | No | Accent colour as hex or a colour name, e.g. #7A3E9D (default), navy, teal. | |
| guests | Yes | The guest list: an array of names ("Jane Doe"), an array of objects ({first, last, company, table}), or pasted text with one guest per line or CSV with a header such as first,last,company,table. Example: ["Jane Doe, Acme Corp, Table 4", "Raj Patel"]. | |
| event_name | No | Same as event; used when event is not sent. | |
| show_table | No | Print table numbers when the list has them. Default true; send false to hide them. | |
| show_company | No | Print the company or role line. Default true; send false to hide it. |
| Name | Required | Description |
|---|---|---|
| sort | Yes | |
| event | Yes | |
| notes | Yes | |
| paper | Yes | |
| style | Yes | |
| accent | Yes | |
| guests | Yes | |
| downloads | Yes | |
| tent_size | Yes | |
| tent_pages | Yes | |
| assumptions | Yes | |
| badge_layout | Yes | |
| badge_sheets | Yes | |
| ignored_lines | Yes | |
| preview_names | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description doesn't need to. It adds real behavioral context beyond them: which two PDF artifacts are generated, the per-sheet layout, that a preview is returned, and that all parameters except the guest list are optional defaults. It stops short of stating pagination or size limits on the guest list.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The trigger, required input, optional extras and exclusions appear in that order, with no filler sentences. It is dense but each clause carries information; the only mild redundancy is restating the output artifacts that the output schema also covers.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 9-parameter tool with one required parameter, rich schema descriptions, an output schema and annotations, this description covers trigger, inputs, defaults, outputs and negative scope. Nothing an agent needs in order 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.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so per-parameter details are already documented and the baseline is 3. The description still adds framing value by telling the agent to send the entire guest list in one call in any of several shapes (names, objects, pasted lines, CSV with header) and that everything else is optional — guidance that prevents unnecessary clarification round-trips.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and a concrete resource set — printable name tags, badges, place cards, table tents — and names the required input. It also states precisely what is produced (name badge PDF at 8 per sheet, folded tent card PDF at 2 per page, plus a preview), so an agent knows exactly what calling it yields.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives an explicit trigger ('Use this when the user wants printable name tags...') and explicit exclusions ('Does not make address labels, business cards, seating charts or wristbands'). Even without sibling tools to route between, the when/when-not boundary is genuinely useful for deciding whether this tool is the right target at all.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
generate_name_tagsMake event name badges from an Excel/CSV roster: 150+ design styles, role colors, A4 print.
Print address labels from a list or a spreadsheet without opening Word.
Make printable business cards from your name and contact details.
Add one secure layer between your agents and this server.