Skip to main content
Glama

list_contacts

Read-only

Retrieve a compact, paged list of friends and groups with IDs and display names. Set refresh=true after adding friends or joining groups to bypass the cache and get updated contacts.

Instructions

Compact list of all friends and/or groups (target id + display name), with paging. Use refresh=true after adding friends/joining groups.

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
kindNoWhich listall
limitNoMax items
offsetNoSkip this many
refreshNoBypass the 5-minute cache

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds behavioral context the annotations cannot: results are compact (only id + display name), results are paged, and a 5-minute cache exists that refresh bypasses. It doesn't state ordering or the page-size ceiling behavior, which keeps it from a 5.

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?

Two short sentences: the first front-loads what is returned and the paging constraint, the second gives the refresh rule. No filler, nothing repeated from the schema verbatim.

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 read-only list tool with full schema coverage and clear annotations, this covers purpose, return shape, paging, and cache invalidation. Minor gaps remain around ordering and whether friends and groups are interleaved under kind=all, but nothing essential to a correct call is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description earns extra by giving the operational trigger for refresh ('after adding friends/joining groups') rather than just restating that it bypasses the cache. The kind/limit/offset semantics are left entirely to the schema, which is acceptable at full coverage.

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 ('Compact list of all friends and/or groups') and even names the returned fields (target id + display name) plus paging. It implicitly separates itself from the single-purpose sibling get_friend_list/get_group_list by offering a combined, compact listing, though it never names an alternative explicitly.

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?

Provides one concrete usage rule: 'Use refresh=true after adding friends/joining groups.' That is genuinely actionable, but there is no guidance on when to pick this combined list versus get_friend_list, get_group_list, or list_recent_chats, and no exclusions.

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

Deploy Server

Other Tools