meetergo-mcp

get_contact

Retrieve a contact's full record including linked appointments and form answers using contact ID or attendee ID from a booking webhook.

Instructions

Get a contact's full record (incl. linked appointments and form answers). Look up by contact_id OR by attendee_id (from a booking webhook).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_contact"
  }
}

Input Schema

Name	Required	Description	Default
`contact_id`	No
`attendee_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jul 8, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description discloses that the tool returns linked appointments and form answers. However, it does not mention what happens if neither parameter is provided, authorization requirements, or error handling, which are important for a read tool.

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?

Two sentences, front-loaded with the primary purpose, and efficient with no redundant words. Every sentence earns its place.

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?

Given no annotations or output schema, the description covers the key behaviors and parameters. Lacks details on return format or error conditions, but sufficient for a simple lookup tool.

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

Parameters4/5

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

Schema coverage is 0%, so the description compensates by explaining the purpose and context for each parameter (contact_id vs. attendee_id from webhook). This adds meaning beyond the bare schema names.

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 clearly states the tool retrieves a contact's full record including linked appointments and form answers. It also specifies the two lookup methods (by contact_id or attendee_id), which distinguishes it from sibling tools like search_contacts.

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?

The description explains when to use each parameter: contact_id for general lookup, attendee_id from a booking webhook. It implies when not to use (e.g., for searching, use search_contacts), but doesn't explicitly exclude other scenarios.

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