nc-mcp-server

remove_file_reminder

DestructiveIdempotent

Remove an active reminder from a Nextcloud file by providing its numeric file ID. Returns a confirmation message, or an error if no reminder is set.

Instructions

Remove the reminder set on a file.

Fails with "No reminder is set" if the file has no active reminder.

Args: file_id: Numeric Nextcloud file id.

Returns: Confirmation message.

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": {
      "file_id": "<file_id>"
    },
    "name": "remove_file_reminder"
  }
}

Input Schema

Name	Required	Description	Default
`file_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description doesn't need to restate those. It adds value by disclosing the specific failure mode ('No reminder is set') and confirming the operation targets an active reminder. This is useful behavioral context beyond the annotations.

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 compact and front-loaded: the core action is in the first sentence, followed by the key failure condition, then the parameter and return value. Every sentence earns its place with no filler.

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 single-parameter, idempotent destructive operation, the description covers the action, the failure mode, the parameter semantics, and the return type. It doesn't describe the exact confirmation message format, but the output schema exists and the operation is simple enough that this is a minor 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?

Schema description coverage is 0%, so the description must compensate. It does: 'file_id: Numeric Nextcloud file id' adds the type (numeric) and the system context (Nextcloud) that the bare integer schema lacks. With only one parameter, this is sufficient.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Remove the reminder set on a file') with a specific verb and resource. It is distinct from sibling tools like set_file_reminder and get_file_reminder, and the error condition ('Fails with "No reminder is set"') further clarifies its exact scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool: when a file has an active reminder that needs removal. It doesn't explicitly name alternatives or exclusions, but the sibling set (get_file_reminder, set_file_reminder) makes the context clear. The error message also tells the agent what happens if used inappropriately.

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

Deploy Server