Skip to main content
Glama

CSV to vCard API - contacts spreadsheet to .vcf

csv_to_vcard
Read-onlyIdempotent

Convert a contact list (CSV/Excel with columns like Name, Phone, Email, Company) into a .vcf file for phones and address books. vCard 3.0 or 4.0. Processed in memory, nothing stored. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.005 per call via x402 at https://radarbg.com/x402/csv-to-vcard.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fileName": "contacts.csv",
      "fileContent": "TmFtZTtQaG9uZTtFbWFpbApBbm5hIEV4YW1wbGU7KzM1OSA4ODggMDAwIDAwMDthbm5hQGV4YW1wbGUuY29tCg=="
    },
    "name": "csv_to_vcard"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNoOr several files: [{fileName, fileContent (base64)}]
versionNovCard version3.0
fileNameNoFile name with extension, e.g. report.pdf
fileContentNoThe file as base64 (a data: URI is fine)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, but the description adds real context beyond them: in-memory processing, immediate file deletion, no storage, a 25 calls/day free tier, and x402 paid pricing. These operational traits are exactly what an agent needs before sending user contact data, though the statement 'nothing stored' is repeated twice and no file-size or processing-time behavior is disclosed.

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 text is front-loaded with the conversion purpose and the format options before pricing, which is the right order. It loses a point for the duplicated privacy claim ('Processed in memory, nothing stored' followed by 'files are deleted right after the call, nothing stored'), which spends words without adding information.

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 four-parameter, no-output-schema conversion tool, the description covers the input shape, supported output versions, privacy handling and cost model. It stops short of describing how the resulting .vcf is returned to the caller (inline content, base64, or a link) and any size limits, which are the remaining gaps an agent might need.

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 the version enum and the files array are already documented, and the description only restates that both vCard 3.0 and 4.0 are supported. It adds nothing about the fileName/fileContent encoding beyond what the schema says, and the schema's own example ('e.g. report.pdf') is not corrected for this contacts-specific tool.

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 states a specific verb and resource: converting a contact list (CSV/Excel with Name, Phone, Email, Company columns) into a .vcf file for phones and address books. It also names the supported vCard versions, so an agent can distinguish this from sibling tools like csv_splitter or data_convert without inspecting the schema.

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 rather than stated: the description makes clear it is for contact spreadsheets and mentions phone/address book consumption, but it never says when to prefer this over siblings such as csv_splitter or data_convert, nor any input constraints or exclusions. The pricing and quota lines inform cost but are not when-to-use guidance.

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.

Resources