Skip to main content
Glama

List contacts

nextcloud_list_contacts
Read-onlyIdempotent

List contacts from a specified Nextcloud address book, returning names, emails, phone numbers, and organizations for directory lookup or sync tasks.

Instructions

List the contacts of one address book with name, emails, phones and organization.

REPORT /remote.php/dav/addressbooks/users/{user}/{book}

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": {
      "address_book_url": "<address_book_url>"
    },
    "name": "nextcloud_list_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
address_book_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.4

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds what data comes back (name, emails, phones, organization) and hints at the underlying WebDAV REPORT call, but says nothing about pagination, result limits, or error behavior for an invalid book URL.

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?

Front-loaded with the action and return fields in one efficient sentence. The second line ('REPORT /remote.php/dav/addressbooks/users/{user}/{book}') is terse and cryptic but does carry the URL format, so it earns its place, if poorly labeled.

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 one-parameter read tool with full annotations and no output schema, listing the returned fields is genuinely useful. However, the description omits the prerequisite of discovering the address book URL and gives no hint about result size, leaving the agent to infer the call sequence from sibling names.

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?

The single parameter address_book_url has 0% schema description coverage, so the description must compensate. It does partially: 'one address book' plus the '/remote.php/dav/addressbooks/users/{user}/{book}' line conveys the expected URL shape, but it never states that the value must be a full URL or how to derive it.

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?

Names a specific verb and resource ('List the contacts of one address book') and enumerates the returned fields (name, emails, phones, organization), which distinguishes it from nextcloud_create_contact/update_contact. It does not distinguish itself from nextcloud_get_contact, and the relationship to nextcloud_list_address_books is left implicit.

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?

No explicit when-to-use or when-not guidance. The description implies the tool works on 'one address book', but never says to call nextcloud_list_address_books first to obtain the required URL, nor when to prefer nextcloud_get_contact for a single record.

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