QR Branding

Build a vCard QR

qr_build_vcard

Read-onlyIdempotent

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.

Changed1 schema field changedOct 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "filePath": {
+      "description": "PDF in the stdio package only: local temp file the PDF was written to.",
+      "type": "string"
+    },
+    "format": {
+      "description": "File format the engine rendered: png, svg, jpg, webp or pdf.",
+      "type": "string"
+    },
+    "mimeType": {
+      "description": "MIME type of the rendered file (the engine's contentType).",
+      "type": "string"
+    },
+    "payload": {
+      "description": "The payload string the engine built and the QR encodes (WIFI:..., BEGIN:VCARD..., geo:...).",
+      "type": "string"
+    },
+    "resourceUri": {
+      "description": "PDF on the remote server only: URI of the embedded resource block that carries the file.",
+      "type": "string"
+    },
+    "sizeBytes": {
+      "description": "Size of the rendered file in bytes, as reported by the engine.",
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "format",
+    "payload"
+  ],
+  "type": "object"
+}

First observedOct 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, non-open-world operation, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the encoded payload is a vCard and scanning it inserts the contact into a phone's address book, which clarifies the artifact's purpose.

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 tight sentences with no filler: the first states what is encoded, the second states the end-user effect. The core action is front-loaded.

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

Completeness4/5

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

With an output schema present and rich annotations, the description need not explain return values or safety. It covers what is built and the user-facing outcome; the only minor omission is which field is required (firstName), which the schema's required list still supplies.

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 every parameter is already documented in the schema with its required flag and format constraints. The description merely re-lists the same field names (name, organization, phone, email, URL) without adding syntax, format, or requirement guidance, so the baseline 3 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 specific verb ('Encode') and resource ('contact card (vCard)'), then enumerates the exact fields encoded. Combined with the tool name, an agent can immediately distinguish this from the geo/wifi QR builders among its 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?

Usage is only implied: the tool should be used when a scannable contact card is wanted. With six siblings (qr_generate, qr_generate_ai, qr_build_geo, etc.) there is no explicit statement of when to pick this one over the generic qr_generate or a template-based builder.

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

All QR Branding tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?