nc-mcp-server

get_file_reminder

Read-onlyIdempotent

Check a file's reminder due date by providing its numeric ID. Returns an ISO 8601 timestamp, or null for no reminder or missing files.

Instructions

Get the reminder set on a specific file.

Returns the due date as an ISO 8601 timestamp, or null if no reminder is set for the file. Also returns null when the file does not exist — the Nextcloud API does not distinguish the two cases, so this tool cannot be used to check file existence.

Args: file_id: Numeric Nextcloud file id. Get this from list_directory, search_files, or any tool that returns file metadata.

Returns: JSON object with file_id and due_date. due_date is null when no reminder is set.

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": "get_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.8/5.0

Behavior5/5

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

Annotations already mark the tool read-only/idempotent, and the description adds crucial ambiguity disclosure: null means either no reminder or nonexistent file, so the tool cannot serve as an existence check. It also specifies the exact return shape (file_id and due_date) and null behavior for due_date.

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 tightly organized with a one-line summary, Args section, and Returns section, and every sentence adds information. The critical ambiguous-null caveat is front-loaded after the summary rather than buried.

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 single-parameter read tool, the description covers purpose, parameter provenance, return semantics, and edge-case behavior. The output schema and annotations cover safety, and nothing an agent needs to invoke it correctly is missing.

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?

The schema only declares file_id as an integer with no description (0% coverage), so the description carries the burden. It explains that file_id is a numeric Nextcloud file id and tells the agent exactly where to source it—list_directory, search_files, or file metadata. This fully compensates for the bare schema.

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?

Description opens with 'Get the reminder set on a specific file,' naming a specific verb and resource. It clearly distinguishes itself from sibling mutators set_file_reminder and remove_file_reminder by focusing on retrieval.

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 states when to use it: to retrieve a file's reminder due date, and gives an explicit exclusion—it cannot be used to check file existence because nonexistent files also return null. It also directs the agent to obtain file_id from list_directory or search_files. It does not explicitly contrast with set_file_reminder/remove_file_reminder, but the retrieval-vs-mutation distinction is clear.

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

Deploy Server