Skip to main content
Glama

List address books

nextcloud_list_address_books
Read-onlyIdempotent

List every address book in a Nextcloud account to identify available contact collections for reading or managing contacts.

Instructions

List the account's address books.

PROPFIND /remote.php/dav/addressbooks/users/{user}

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.4

TDQS

A3.5/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 fully covered without the prose. The description's only extra behavior signal is the raw PROPFIND endpoint, which suggests a live WebDAV query against the user's collection; it says nothing about whether shared/other users' address books appear or how the result is shaped.

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?

Two lines, front-loaded with the purpose, with no filler or repetition. The raw endpoint line is compact and adds a hint of implementation context, though for most callers it is the least earning part of the definition.

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 zero-parameter read that is fully covered by annotations, the definition is serviceable, but there is no output schema and the description does not say what an address book record contains (names, IDs/URIs, default flags) — information an agent needs in order to pass a valid identifier to a contact-creating sibling. That is the main gap.

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?

The tool takes zero parameters and the schema is a closed empty object at 100% coverage, so there is nothing for the description to clarify. Baseline 4 applies; the {user} placeholder in the endpoint line is resolved implicitly and needs no further documentation.

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 gives a specific verb and resource ("List the account's address books") and even names the underlying DAV collection, so an agent knows exactly what entity is enumerated. It does not, however, contrast itself with the neighboring contact/calendar listing tools (e.g. nextcloud_list_contacts), so the account-vs-contents distinction must be inferred from names alone.

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: an agent can deduce this is the discovery step before nextcloud_create_contact or nextcloud_update_contact, but the description never says so. There are no explicit when-to-use, when-not-to-use, or alternative-tool statements, and no note about what account/DAV context is required.

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