Skip to main content
Glama
Sign In
Google Workspace MCP VE

Google Workspace MCP VE

by HuntsDesk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_contact

Retrieve a complete contact record including emails, phones, organizations, and addresses by providing a contact ID. Use after listing or searching contacts to get full details.

Instructions

Fetch a single contact with all details (emails, phones, orgs, addresses).

Use this when you already have a contact ID from list_contacts or search_contacts and need the full record (including notes, addresses, multiple emails/phones). For creating/updating use manage_contact. Requires the contacts.readonly OAuth scope.

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

Input Schema

NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
contact_idYesContact ID — either the short form ("c1234567890") or the full resource name ("people/c1234567890"). The short form is auto-prefixed.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • changedInput schema / properties / contact_id / description
      Previous value: -"The contact ID (e.g., \"c1234567890\" or full resource name \"people/c1234567890\")."New value: +"Contact ID — either the short form (\"c1234567890\")\nor the full resource name (\"people/c1234567890\"). The short\nform is auto-prefixed."
    • changedInput schema / properties / user_google_email / description
      Previous value: -"The user's Google email address. Required."New value: +"The user's Google email address (authenticated\naccount)."
  2. First observedv1.19.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses the required OAuth scope (contacts.readonly), implying a read-only operation. While it does not detail side effects (none expected), it adequately conveys the tool's safe, non-destructive nature.

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?

The description is four sentences, front-loaded with the core purpose. Every sentence adds value: purpose, usage context, alternative tool, and authentication requirement. No redundancy or filler.

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

Completeness5/5

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

Given that an output schema exists, the description need not detail return values. It covers purpose, usage, alternatives, and authentication. For a simple fetch tool, the description is fully complete and leaves no ambiguity.

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 coverage is 100% with clear parameter descriptions. The description adds no new parameter information beyond what the schema provides, resulting in minimal added value. Baseline score of 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?

The description begins with 'Fetch a single contact with all details,' using a specific verb and resource. It lists included data fields (emails, phones, orgs, addresses) and distinguishes from sibling tools like list_contacts (which returns summaries) and manage_contact (for create/update).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance: 'Use this when you already have a contact ID from list_contacts or search_contacts and need the full record.' It also directs to manage_contact for creating/updating, providing clear when-to-use and when-not-to instructions.

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

Deploy Server

Other Tools