Skip to main content
Glama

List list contacts

list_list_contacts
Read-onlyIdempotent

Page through a list's contacts, most recently added first.

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": {
      "id": "<id>"
    },
    "name": "list_list_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesList id
limitNoMax results (default 25, max 100)
cursorNonext_cursor from the previous page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"next_cursor from the previous page"
    • addedInput schema / properties / limit / description
      Added value: +"Max results (default 25, max 100)"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description still earns credit for disclosing two behaviors not in the annotations: the deterministic ordering (most recently added first) and that results are paginated. It stops short of describing rate limits or the shape of each returned contact entry.

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?

A single front-loaded sentence with zero filler; the verb, scope, and ordering each pull their weight.

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 paginated read with all params documented and safety covered by annotations, the description is nearly sufficient; the cursor/limit paging contract is left implicit but inferable from the schema. No return-shape note is required since there is no output schema, though a hint about what each contact entry contains would have capped this at 5.

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 all three params described (id, limit with default/max, cursor referencing next_cursor), so the schema carries the semantics. The description adds only the ordering guarantee and the paging behavior, not any detail on limit or cursor handling — the baseline 3 for full coverage 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?

States a specific verb and resource ('Page through a list's contacts') plus ordering ('most recently added first'), which is enough to distinguish it from the sibling list_contacts that lists all contacts. It doesn't explicitly name that sibling, so it falls short of the top mark.

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 implied by the phrase 'a list's contacts', which tells the agent it needs a list id, and the 'page through' wording signals repeated calls. There is no explicit when-to-use statement or named alternative (e.g. list_contacts for workspace-wide), so guidance is only inferred.

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.