Skip to main content
Glama

create_vcard_payload

Idempotent

Create standard vCard text suitable for QR encoding from contact fields.

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": {
      "fullName": "<fullName>"
    },
    "name": "create_vcard_payload"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
emailNo
phoneNo
titleNo
addressNo
websiteNo
fullNameYesContact display name. Required.
organizationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and side-effect profile is covered structurally. The description adds that the result targets QR encoding, which is useful framing, but says nothing about which vCard version is emitted, how empty optional fields are handled, or any size/folding limits relevant to QR. Reasonable but not rich.

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?

A single twelve-word sentence with the resource front-loaded and zero filler. Nothing to trim and nothing buried.

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

Completeness2/5

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

With 8 parameters at 13% schema coverage and no output schema, the description should carry most of the explanatory burden, yet it does not describe the produced vCard structure or how each contact field maps into it. An agent can call it, but cannot predict the output or know which fields are meaningful.

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

Parameters2/5

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

Schema description coverage is only 13% — just fullName documents itself. The phrase 'from contact fields' names no individual parameter and gives no formatting rules for phone, address, email, or website, leaving 7 of 8 parameters with no semantic guidance in either place.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Create standard vCard text') and adds the downstream purpose ('suitable for QR encoding'), so the agent knows exactly what is produced. It does not reference the only sibling (get_product_context), but that tool is unrelated, so no differentiation is really needed.

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 implied by the output framing — call this when you need a vCard string to feed a QR encoder — but there is no explicit when/when-not guidance, no prerequisites, and no note on what to do if the contact lacks optional fields. Minimum viable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.