John's Essentials

generate_business_card

Business Card Generator — Generate a printable business card (PDF or PNG) from name, job title, company, and contact details. [category: generate]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`email`	No	Printed verbatim in the contact block — no validation, no mailto link; empty = line omitted.
`phone`	No	Printed verbatim in the contact block; empty = line omitted. No formatting applied.
`format`	No	'pdf' (default) or 'png' (300 DPI Ghostscript raster, 1050x600). Any other value silently returns the PDF.	pdf
`company`	No	Printed under the name; omitted entirely when empty. Latin-1 only — CJK/emoji glyphs render as '.'.
`website`	No	Printed exactly as sent — strip 'https://' yourself if unwanted; empty = line omitted.
`fullName`	Yes	Full name printed on the card. Field name is 'fullName' — not 'name'.
`jobTitle`	No	Job title. Field name is 'jobTitle' — not 'title'.
`template`	No	Card layout.	modern
`primaryColor`	No	Hex color WITHOUT the leading '#'.	1a1a2e
`secondaryColor`	No	Hex color WITHOUT the leading '#'.	E05535

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026
- addedInput schema / properties / jobTitle / x-ui
```
Added value: +{
+  "unset_label": "Left off the card"
+}
```

Changed2 schema fields changedSep 11, 2026

changedInput schema / properties / template / description

Previous value: -"Card template, e.g. modern or classic."New value: +"Card layout."

addedInput schema / properties / template / enum

Added value: +[
+  "modern",
+  "classic",
+  "minimal",
+  "creative",
+  "corporate",
+  "elegant"
+]

First observedSep 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With annotations already marking the operation as non-read-only but non-destructive, the description adds limited behavioral context: it discloses that the output is printable and can be PDF or PNG. It does not explain side effects, file handling, or post-generation behavior, but this is partially acceptable given the annotations.

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 a single front-loaded sentence that communicates the core purpose immediately. The 'Business Card Generator' prefix slightly repeats the tool name, but it does not bloat the description or obscure the actionable content.

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

Completeness3/5

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

All 10 parameters are thoroughly documented in the schema, which carries most of the burden. However, there is no output schema and the description does not mention what the tool returns or where the generated card goes, which is a noticeable gap for a generator tool.

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 100%, and the schema already documents default values, enum options, formatting behavior, and constraints such as Latin-1 encoding and omitted lines. The description only summarizes the input categories and adds little semantic value beyond the schema.

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 states a specific verb ('Generate'), a clear resource ('printable business card'), and the output formats (PDF or PNG). It also lists the main input fields, making it easy to distinguish from the many other generate_* siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The use case is implied strongly by 'Business Card Generator' and 'Generate a printable business card', but there is no explicit guidance about when to use this tool versus alternatives such as generate_certificate or generate_placeholder_image. No exclusions or alternative routing are provided.

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

All John's Essentials 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?