MyClaw Toolkit MCP Server

vcard_generator

Generate vCard (.vcf) contact files from name, phone, email, and organization inputs.

Instructions

Generate vCard (.vcf) contact files

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

Input Schema

Name	Required	Description
`name`	Yes	Full name
`phone`	No	Phone number
`email`	No	Email address
`org`	No	Organization/company

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Jun 23, 2026

TDQS

C2.7/5.0

Behavior1/5

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

No annotations are present, and the description only says 'generate vCard files'. It omits critical behavioral details: whether it returns the file content or saves it, any limitations on data size, or required permissions. The agent is left guessing how the tool operates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise and front-loaded. However, it sacrifices necessary depth for brevity.

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?

Given the lack of an output schema, the description should explain what the tool returns (e.g., .vcf file content as text). It does not. Parameter descriptions are adequate but no usage context is provided.

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 coverage is 100%, so the schema already describes all parameters. The description adds no extra meaning beyond what the schema provides, hence the baseline score of 3.

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 'Generate vCard (.vcf) contact files' clearly states the verb and resource, matching the tool name. It distinguishes the tool from siblings like qrcode or wifi_qrcode, though it could be more specific about the output.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives, such as other formatting or encoding tools in the siblings list. There are no exclusions or context for invocation.

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