Skip to main content
Glama

List contacts

contact_list
Read-onlyIdempotent

List this organisation's contacts, newest or by-name first. Filter by channel, free-text search, or restrict to a given user's assigned contacts. Read only.

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

Input Schema

NameRequiredDescriptionDefault
pageNo0-based page number, default 0
sizeNoPage size, default 20
searchNoFree-text match on name or company
sortByNoField to sort by, e.g. "name". Default "name"
channelNotelephony, whatsapp, rcs or email
recentDaysNoOnly contacts with activity in the last N days
unreadOnlyNoOnly contacts with an unread message
sortDirectionNoDefault "asc"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/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=false, and the description's contribution is the redundant phrase 'Read only.' Nothing is added about pagination behavior, default result ordering mechanics, rate limits, or what a returned contact record looks like, so it does little beyond the structured metadata.

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?

Three short sentences, front-loaded with the resource and ordering, then the filter options, then the safety note. There is little waste, though the trailing 'Read only.' duplicates the annotations and one clause describes a filter that does not exist.

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 an 8-parameter read-only list tool with no output schema, the description covers the high-level purpose and some filters but omits pagination defaults, the meaning of recentDays/unreadOnly, and any hint of the returned record shape. The phantom assigned-user filter leaves the definition internally inconsistent rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description actively mentions a filter that has no corresponding parameter ('restrict to a given user's assigned contacts') and a 'newest' ordering that maps to no documented sort value, while saying nothing about page, size, recentDays, unreadOnly, or sortDirection. This both under-explains the real parameters and sets a false expectation about an unavailable one.

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 opens with a specific verb and resource ('List this organisation's contacts') and states sort order, so the core operation is unambiguous. It does not, however, distinguish itself from the sibling contact_search or contact_detail, even though free-text search is mentioned as a filter here.

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 through the filter list: 'Filter by channel, free-text search, or restrict to a given user's assigned contacts' suggests browsing/listing scenarios, but there is no explicit when-to-use-this vs contact_search, and no exclusions or prerequisites are given.

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.