Skip to main content
Glama

get_contact

Read-onlyIdempotent

Retrieve full details for a single Google Contact using its resourceName. Use this to look up a specific person's complete contact information.

Instructions

Get full details for a single Google Contact by resourceName.

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

Input Schema

NameRequiredDescriptionDefault
resourceNameYesContact resourceName (e.g. 'people/c123456789')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered without description help. The description adds only that the full record is returned, and says nothing about lookup failure behavior or whether stale/missing resourceNames error out.

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?

One sentence, front-loaded with the verb and resource, with no filler or restated title. Every element earns its place for a single-parameter read tool.

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?

For a simple one-parameter read with rich annotations and no output schema, the description covers what is needed to invoke it correctly. The remaining gap — how to source a resourceName and what a not-found result looks like — is small but real.

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 the single parameter is already documented with an example value ('people/c123456789'), so the schema carries the load. The description only echoes the parameter name, adding no format or validation detail beyond it — baseline 3.

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?

States a specific verb+resource ('Get full details for a single Google Contact') plus the identifier it operates on (resourceName), and the word 'single' implicitly separates it from list_contacts and search_contacts. It stops short of naming a sibling or explicitly contrasting scope, so it falls just short of a 5.

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: fetch one contact when you already have its identifier. The description never says how to obtain a resourceName (e.g., via list_contacts or search_contacts) or what to do when the contact is unknown, which are the two decision points an agent actually faces with this sibling set.

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