QR for Agent

update_vcard_qr

Update contact details in an existing vCard QR code without regenerating the image. Modify name, organization, email, phone, or other fields; changes apply directly to the QR.

Instructions

Update the contact details of a vCard QR code. Only works on QR codes created with type='vcard'. Partial updates merge with existing data. Note: updating vCard data changes the QR image content.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "short_id": "<short_id>"
    },
    "name": "update_vcard_qr"
  }
}

Input Schema

Name	Required	Description
`short_id`	Yes	The short ID of the vCard QR code to update.
`first_name`	No	Contact first name.
`last_name`	No	Contact last name.
`organization`	No	Company or organization.
`title`	No	Job title.
`email`	No	Email address.
`phone`	No	Phone number.
`url`	No	Website URL.
`address`	No	Street address.
`note`	No	Additional notes.
`label`	No	Update the label.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description reveals key behaviors: partial updates merge with existing data and updating vCard data changes the QR image content. This adds value beyond the schema.

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 efficiently cover purpose, constraints, and behavior. No wasted words, and the most critical information 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?

Given 11 simple parameters, no output schema, and no annotations, the description sufficiently explains scope, update semantics, and side effects. It could mention that all fields except short_id are optional, but required field is already indicated in schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds extra context like 'Partial updates merge with existing data' and the type constraint, enhancing understanding beyond schema. It does not repeat schema descriptions.

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 clearly states the verb 'Update', resource 'contact details of a vCard QR code', and specifies it only works on QR codes created with type='vcard', distinguishing it from other update tools for different types.

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?

It explicitly states the precondition 'Only works on QR codes created with type='vcard'', which guides when to use it. However, it does not explicitly list alternatives or when not to use it, but sibling context provides implicit differentiation.

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