Skip to main content
Glama

Get contact

get_contact
Read-only

Retrieve full details of a personal contact by ID to view stored information such as email addresses, phone numbers, and other contact data.

Instructions

Get all details of a personal contact.

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

Input Schema

NameRequiredDescriptionDefault
idYesContact ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The phrase "all details" adds the useful signal that a full record is returned rather than a summary, but there is no mention of behavior for a missing or invalid contact ID, nor of any return shape.

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 compact sentence with the verb and scope front-loaded and no filler. It is efficient, though it errs toward minimalism rather than maximally informative.

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

Completeness3/5

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

For a one-parameter, read-only tool with full schema coverage and no output schema, this is adequate but thin. An agent can call it correctly, yet nothing describes the returned detail set or error behavior for a nonexistent ID.

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%, with the single id parameter documented as "Contact ID", so the baseline is 3. The description adds no format hints or guidance on where the ID comes from (e.g., from list_contacts), so it does not exceed the schema.

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 uses a specific verb and resource ("Get all details of a personal contact"), and the qualifier "personal contact" separates it from list_contacts or event/message getters in the sibling set. It stops short of naming a sibling explicitly, but the single-record retrieval intent is unambiguous.

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 only implied: the singular "a personal contact" combined with a required id suggests fetching one record by ID rather than listing, but nothing states when to prefer this over list_contacts or what to do if the ID is unknown. No prerequisites or exclusions are given.

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