Skip to main content
Glama

parse_and_upsert_contact

Idempotent

Extract structured contact details from vCard, HTML, CSV, JSON, or freeform text and optionally save or merge them into Google Contacts.

Instructions

Parse one or more contacts from raw text or markup (vCard/.vcf, HTML, Markdown, CSV, JSON, email signature, or freeform text) and optionally save (upsert) them to Google Contacts.

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

Input Schema

NameRequiredDescriptionDefault
inputYesRaw text or markup containing contact info (vCard, HTML, Markdown, CSV, JSON, email signature, or notes)
mergeNoMerge with existing contact if found (default: true)
dryRunNoIf true, only parses and returns the extracted structured contact(s) without writing to Google Contacts (default: false)
formatNoInput format hint (defaults to 'auto')auto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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=true, so safety is covered. The description adds the upsert-to-Google-Contacts destination and the write-optional framing, consistent with idempotentHint. It stops short of saying what happens when several contacts are parsed at once, how merges resolve conflicting fields, or whether Google authentication is a prerequisite.

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?

A single front-loaded sentence with the action first and the format parenthetical second; no filler or restated title. The format enumeration is long but each item genuinely widens what an agent will consider valid input.

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?

With no output schema, the description should hint at the return shape, and 'parses and returns the extracted structured contact(s)' in the dryRun parameter plus the 'one or more contacts' phrasing covers cardinality reasonably. The remaining gap is operational: it never mentions that Google authentication is required for the write path, which matters for a tool that touches an external account.

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% and all four parameters (input, merge, dryRun, format) are documented inline with defaults and an enum, so the schema does the heavy lifting. The description adds nothing parameter-specific beyond naming the input formats, which the schema also lists. Baseline 3 is appropriate.

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?

States a specific verb pair ('parse ... and optionally save (upsert)') with a concrete resource ('Google Contacts') and enumerates every accepted input format (vCard, HTML, Markdown, CSV, JSON, email signature, freeform text). That format list implicitly separates it from image-based extraction and from structured-field upsert siblings, so an agent can pick it without opening another 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?

The phrase 'optionally save' signals both the parse-only and write modes, which is real context. But it never states when to prefer this over upsert_contact (already-structured data) or extract_contact_from_image (image sources), and offers no exclusion or precondition guidance.

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