Skip to main content
Glama

get_contact

Read-only

Retrieve one contact's full details by ID—name, organization, job title, emails, phones with labels, postal addresses, and birthday—while excluding notes.

Instructions

Get one contact with all details: name, organization, job title, emails and phones with labels, postal addresses and birthday. Notes are never returned.

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 from search_contacts. Use it as given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value beyond that by enumerating the returned fields and stating a hard constraint, 'Notes are never returned,' which an agent cannot learn from annotations or schema. It does not describe error behavior when an id is unknown.

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 action and payload, then the exclusion caveat. Every clause carries information; nothing is filler.

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 usefully encapsulates the return shape by listing name, organization, job title, emails/phones with labels, addresses, and birthday, plus the notes exclusion. Slightly incomplete around not-found or permission behavior, but adequate for a simple annotated read tool.

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?

Only one parameter with 100% schema description coverage, so the schema already explains the id and its origin. The description adds no additional meaning about the id, matching the baseline for fully documented schemas.

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?

Specific verb and resource ('Get one contact') followed by an enumeration of the fields returned, which lets an agent distinguish this single-record fetch from list/search siblings. It does not name an alternative tool outright, but the scope 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: 'get one contact' versus list/search behavior, and the schema note that the id comes 'from search_contacts' sketches the workflow. There is no explicit when-to-use or when-not-to-use statement in the description itself.

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