nc-mcp-server

get_contacts

Read-onlyIdempotent

Retrieve contacts from a Nextcloud address book with pagination. Specify a book ID, limit, and offset to filter results, returning contact details like names, emails, phones, and addresses.

Instructions

Get contacts from an address book.

Args: book_id: Address book ID (default "contacts"). Use list_addressbooks to find IDs. limit: Maximum number of contacts to return (1-500, default 50). offset: Number of contacts to skip for pagination (default 0).

Returns: JSON with "data" (list of contact objects with uid, full_name, name, emails, phones, addresses, organization, title, note) and "pagination" (count, offset, limit, has_more).

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

Input Schema

Name	Required	Default
`limit`	No
`offset`	No
`book_id`	No	contacts

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile. The description adds useful behavioral detail on top: pagination semantics (offset, limit, has_more) and the exact shape of returned contact objects. This exceeds annotation coverage without contradicting it.

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?

The description is structured as a docstring with a one-line summary followed by Args and Returns sections. There is no filler, every clause carries information, and the purpose is front-loaded in the first sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list operation with an output schema present, the description is complete: it explains all three parameters with defaults, describes the return payload in detail, and notes how to discover valid book IDs. No critical information is missing for an agent to call it successfully.

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

Parameters5/5

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

Schema description coverage is 0%, but the description fully compensates. Each parameter is explained with defaults and constraints: book_id (with pointer to list_addressbooks), limit (1-500, default 50), offset (pagination behavior, default 0). This is exactly what the schema lacks.

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 states a clear verb+resource combination: 'Get contacts from an address book.' The return shape and pagination fields make it unambiguous that this is a list operation. However, it doesn't explicitly differentiate from the sibling get_contact (singular), relying on the tool name to signal the distinction.

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?

There is no guidance on when to choose this tool over alternatives. The only sibling reference is 'Use list_addressbooks to find IDs,' which is a prerequisite for a parameter, not a tool-selection rule. No mention of get_contact for single-contact lookups or other alternative approaches.

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

Deploy Server