QR Branding

Build a vCard QR

qr_build_vcard

Read-onlyIdempotent

Encode a vCard QR code from a name, organization, phone, email and website so scanning it adds the contact directly to a phone's address book.

Instructions

Encode a contact card (vCard) with first and last name, organization, phone, email and website URL into a QR. Scanning the QR adds the contact to the phone's address book.

Input Schema

Name	Required	Description
`url`	No	Personal or company website URL.
`email`	No	Email address.
`phone`	No	Phone number, including country code (e.g. +1-555-867-5309).
`lastName`	No	Contact's last name.
`firstName`	Yes	Contact's first name.
`organization`	No	Company or organization name.

Output Schema

Name	Required	Description
`format`	Yes	File format the engine rendered: png, svg, jpg, webp or pdf.
`payload`	Yes	The payload string the engine built and the QR encodes (WIFI:..., BEGIN:VCARD..., geo:...).
`filePath`	No	PDF in the stdio package only: local temp file the PDF was written to.
`mimeType`	No	MIME type of the rendered file (the engine's contentType).
`sizeBytes`	No	Size of the rendered file in bytes, as reported by the engine.
`resourceUri`	No	PDF on the remote server only: URI of the embedded resource block that carries the file.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Oct 18, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare this as readOnly, idempotent, non-destructive, and not open-world, so the safety profile is covered. The description adds useful behavioral context by explaining that the output QR, when scanned, adds the contact to an address book.

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?

Two sentences, front-loaded with the core action and followed by the scanning effect. There is no redundant or filler content.

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?

Given the tool's simplicity, full schema descriptions, rich annotations, and the presence of an output schema, the description is complete enough for an agent to understand what the tool produces and why it is used. It does not need to explain return values or permissions in more detail.

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%, so the schema already documents every parameter's meaning and format. The description lists the same fields but does not add syntax, constraints, or other parameter-level meaning beyond what is already in 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 uses a specific verb and resource: 'Encode a contact card (vCard)... into a QR.' It names the exact fields and the resulting behavior, so an agent can distinguish this specialized vCard builder from generic QR generation or sibling builders like qr_build_wifi and qr_build_geo.

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 description implies the use case by stating that scanning the QR adds the contact to a phone's address book. However, it does not explicitly say when to choose this tool over qr_generate or other QR builders, nor does it state exclusions or prerequisites.

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

Deploy Server