Skip to main content
Glama

Hail Communication for AI

List contacts

list_contacts
Read-onlyIdempotent

List workspace members and manually saved contacts.

    Returns ``items`` with ID, kind, name, phone_e164, email and role.
    Members have ``kind="member"``, an ID of ``member:<user_id>`` and a role.
    Manual entries have ``kind="manual"``, a UUID and no role.

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
qNoOnly contacts whose name, email or phone contains this text.
limitNoHow many contacts to return in one reply. Omitted: 100.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Most contacts to return. Omitted: 100."New value: +"How many contacts to return in one reply. Omitted: 100."
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / limit / anyOf
      Previous value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maximum": 500,
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results, 1 to 500. Omitted: 100."New value: +"Most contacts to return. Omitted: 100."
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description goes further by disclosing that the result set is polymorphic (member vs manual), the ID formats for each, and that manual entries carry no role. That is real behavioral context an agent needs to interpret rows correctly, though it overlaps with the available output schema.

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?

Four short, front-loaded sentences with the core purpose stated first and the item-shape details following logically. Slightly redundant given the output schema, but no sentence 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 annotations carrying the safety profile, an output schema carrying the return shape, and all three parameters documented in the schema, the description only needs to frame purpose and record kinds — which it does. Missing only a note on whether results are paged/bounded beyond the schema's default of 100.

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%, so q, limit and llm_model are already fully documented in the schema. The description adds no filtering, paging or model-ID semantics of its own, so the baseline 3 applies.

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 workspace members and manually saved contacts") and immediately disambiguates the two record kinds it returns. It never names the nearest alternative (lookup_contact / create_contact), so the agent must infer the boundary itself.

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 by the word "List"; there is no explicit statement of when to reach for this tool versus lookup_contact for a single record or create_contact for adding one. A reader can guess the intent, but nothing routes them.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources