Skip to main content
Glama
Nextcloud MCP Server

Nextcloud MCP Server

by stack74

Current user and server

nextcloud_whoami
Read-onlyIdempotent

Identify the connected Nextcloud user, including display name, email, groups, quota, server, and whether write operations are permitted; use it before relying on upload, create, move, or delete tools.

Instructions

Who is connected: Nextcloud user, display name, e-mail, groups, storage quota, plus the Nextcloud server and whether this MCP server allows changes (upload, create, move, delete). Call this when unsure whether a write tool should exist.

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_whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the bar is lower, and the description still adds genuine context: it enumerates the identity fields returned and discloses that the call reports whether this MCP server permits mutations. That capability-probing behavior is not derivable from the annotations and is exactly what an agent needs before attempting a write.

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?

Two sentences with no filler: the first enumerates the returned data, the second gives the usage trigger. The most decision-relevant payload (write-capability check) is placed at the end of sentence one and reinforced in sentence two, so it is effectively front-loaded for the primary use case.

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?

There is no output schema, so the description must carry the return-value burden, and it does so by listing the identity fields, the server, and the write-permission flag. For a zero-parameter read-only tool this is close to sufficient; only the exact shape of the response (field names, format of quota) is left unspecified.

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, so there are no parameter semantics to explain; the schema is empty and complete. Nothing in the description misleads about inputs. Baseline 4 applies for a no-argument tool.

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 names a specific resource set: the connected Nextcloud user (user id, display name, e-mail, groups, storage quota), the server, and a write-capability flag. That is concrete enough to distinguish it from the file-oriented siblings (list_files, read_file, download_file), none of which return identity or capability data. It loses the top score only because the verb framing ('Who is connected') is looser than needed and no sibling is named explicitly.

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?

It gives an explicit trigger: 'Call this when unsure whether a write tool should exist.' That is a real when-to-use rule tied to a concrete decision (probe capability before attempting upload/create/move/delete). It does not state when not to call it or offer an alternative, but for a free zero-arg read that is a minor omission.

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