Skip to main content
Glama

list_contacts

Read-onlyIdempotent

List Google Contacts with optional pagination and sort order to browse address book entries page by page.

Instructions

List contacts from Google Contacts with optional pagination and sort order.

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": "list_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageSizeNoNumber of contacts to return (1-1000, default 50)
pageTokenNoPagination token from a previous list_contacts response
sortOrderNoLAST_MODIFIED_DESCENDING

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds only the incremental fact that pagination and sorting are optional; it does not describe the response shape or how pageToken chains requests. That is modest added value on top of the annotations, hence a 3.

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 front-loaded sentence with zero filler that puts the resource and its modifiers in the right order. It is efficient, though its brevity leaves little anchoring detail beyond the core claim.

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 zero-required-parameter, read-only list tool with full annotation coverage, the description is serviceable but thin. It omits what a response contains (contact list plus next-page token) and whether results are capped by default, which would help an agent plan pagination without trial and error.

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 67%, with pageSize, pageToken and the sortOrder enum all documented in the schema itself, so the schema does most of the work. The description only restates that pagination and sort order exist without adding format or default details. Baseline 3 is appropriate.

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 names a specific verb and resource ("List contacts from Google Contacts") and scopes it with pagination and sorting, so the agent knows exactly what the tool returns. It does not, however, distinguish this from the sibling search_contacts, leaving the agent to infer that this is the unfiltered enumeration.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives such as search_contacts or get_contact, even though both overlap in purpose. The phrase "optional pagination and sort order" hints at browsing behavior but never states the condition that selects this tool over its siblings.

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