Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Delete contact

nextcloud_delete_contact
DestructiveIdempotent

Delete a contact from a Nextcloud address book by specifying its URL. Use the confirm flag for destructive operations when client prompts are unavailable.

Instructions

Delete one contact.

DELETE /remote.php/dav/addressbooks/users/{user}/{book}/{contact}.vcf

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": {
      "contact_url": "<contact_url>"
    },
    "name": "nextcloud_delete_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.
contact_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description adds the raw DELETE path, which weakly signals permanence but does not say whether deletion is recoverable, whether missing contacts error out, or how confirm behaves when the client can prompt. Useful but thin beyond annotations.

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 verb and resource, then the endpoint; no filler sentences. The raw HTTP path is arguably implementation noise for an agent, but it is compact and does clarify identifier structure.

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

Completeness2/5

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

A destructive mutation with no output schema and half its parameters undocumented. The description never explains how to source contact_url, whether deletion cascades or is reversible, or what confirms or errors look like, leaving real gaps for a delete operation.

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

Parameters2/5

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

contact_url is completely undocumented in both schema and description, and the description's URL template is the only hint at its format; the required-vs-optional distinction and how to obtain a contact_url (e.g., from nextcloud_list_contacts) are unstated. With 50% schema coverage, the description does not compensate for the gap.

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 ("Delete one contact") and the exact DAV endpoint it hits, distinguishing it from nextcloud_delete_contact_siblings like delete_group or delete_user. It lacks explicit differentiation from nextcloud_update_contact or nextcloud_list_contacts, but the verb+resource pairing is unambiguous.

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 guidance on when to use this versus alternatives, no prerequisites (does the caller need the address book owner's permissions?), and no warning about confirm interaction. The endpoint line is implementation detail, not usage guidance.

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