Skip to main content
Glama
benswel

QR for Agent

update_vcard_qr

Modify contact information in existing vCard QR codes. Change names, organizations, emails, phones, addresses, or notes while preserving the original QR image.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
short_idYesThe short ID of the vCard QR code to update.
first_nameNoContact first name.
last_nameNoContact last name.
organizationNoCompany or organization.
titleNoJob title.
emailNoEmail address.
phoneNoPhone number.
urlNoWebsite URL.
addressNoStreet address.
noteNoAdditional notes.
labelNoUpdate the label.

Implementation Reference

  • The handler function for updating vCard QR code details, which sends a PATCH request to the API.
    handler: async (input: Record<string, unknown>) => {
      const { short_id, label, ...vcardFields } = input;
      const body: Record<string, unknown> = { vcard_data: vcardFields };
      if (label !== undefined) body.label = label;
      return apiRequest(`/api/qr/${short_id}`, { method: "PATCH", body });
    },
  • The Zod schema defining the input parameters for updating a vCard QR code.
    inputSchema: z.object({
      short_id: z.string().describe("The short ID of the vCard QR code to update."),
      first_name: z.string().optional().describe("Contact first name."),
      last_name: z.string().optional().describe("Contact last name."),
      organization: z.string().optional().describe("Company or organization."),
      title: z.string().optional().describe("Job title."),
      email: z.string().optional().describe("Email address."),
      phone: z.string().optional().describe("Phone number."),
      url: z.string().optional().describe("Website URL."),
      address: z.string().optional().describe("Street address."),
      note: z.string().optional().describe("Additional notes."),
      label: z.string().optional().describe("Update the label."),
    }),
  • The tool definition registration for 'update_vcard_qr' in the MCP tools collection.
    update_vcard_qr: {
      description:
        "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.",
      inputSchema: z.object({
        short_id: z.string().describe("The short ID of the vCard QR code to update."),
        first_name: z.string().optional().describe("Contact first name."),
        last_name: z.string().optional().describe("Contact last name."),
        organization: z.string().optional().describe("Company or organization."),
        title: z.string().optional().describe("Job title."),
        email: z.string().optional().describe("Email address."),
        phone: z.string().optional().describe("Phone number."),
        url: z.string().optional().describe("Website URL."),
        address: z.string().optional().describe("Street address."),
        note: z.string().optional().describe("Additional notes."),
        label: z.string().optional().describe("Update the label."),
      }),
      handler: async (input: Record<string, unknown>) => {
        const { short_id, label, ...vcardFields } = input;
        const body: Record<string, unknown> = { vcard_data: vcardFields };
        if (label !== undefined) body.label = label;
        return apiRequest(`/api/qr/${short_id}`, { method: "PATCH", body });
      },
    },
Behavior4/5

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

No annotations provided, so description carries full burden. Successfully discloses merge behavior for partial updates and warns that 'updating vCard data changes the QR image content' (side effect). Missing error handling details (e.g., invalid short_id).

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?

Four sentences, front-loaded with purpose, followed by constraints, behavioral semantics, and side effects. Every sentence earns its place with zero redundancy or fluff.

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?

For a mutation tool with 11 parameters and no annotations/output schema, description adequately covers scope constraints and update behavior. Could improve by mentioning error cases (e.g., non-existent short_id) or return value structure.

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 baseline applies. Description references 'contact details' generally but does not add parameter-specific semantics (format requirements, validation rules) beyond what the schema already documents for the 11 parameters.

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?

Description uses specific verb 'Update' with clear resource 'vCard QR code' and distinguishes from sibling tools (update_wifi_qr, update_app_store_qr, etc.) by specifying 'contact details' and the type='vcard' constraint.

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?

Explicitly states constraint 'Only works on QR codes created with type='vcard'' which defines when to use it. Explains partial update semantics ('merge with existing data'). Does not explicitly name sibling alternatives, though constraint implies them.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/benswel/qr-agent-core'

If you have feedback or need assistance with the MCP directory API, please join our Discord server