Skip to main content
Glama

Get user info

nextcloud_get_user_info
Read-onlyIdempotent

Retrieve the connected Nextcloud account's ID, display name, email, quota, and groups to verify user identity and monitor storage limits.

Instructions

Read the connected account: id, display name, email, quota, groups.

GET /ocs/v2.php/cloud/user

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.4

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered structurally. The description adds the underlying OCS endpoint and the returned field set, but says nothing about error cases (e.g. expired session, insufficient scope) that matter for an account-introspection call. Useful context, not rich behavioral disclosure.

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?

Two short lines, front-loaded with the resource and field list. The raw endpoint path is arguably noise for an agent that only needs to know what the call returns, but it is compact and does not obscure the core statement.

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 zero-parameter, read-only introspection tool with no output schema, the description carries the necessary burden by enumerating the returned fields. The one meaningful gap is that it never contrasts itself with nextcloud_get_user or nextcloud_list_users, which an agent must disambiguate from context alone.

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 is no parameter semantics for the description to explain and the schema is trivially complete. The description correctly adds nothing spurious about inputs, matching the baseline for a no-arg 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 concrete verb and resource ("Read the connected account") and enumerates the returned fields (id, display name, email, quota, groups), so the agent knows exactly what it gets. It stops short of distinguishing itself from the closely named sibling nextcloud_get_user, leaving the 'self vs. arbitrary user' difference to inference.

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

Usage Guidelines3/5

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

"The connected account" implicitly signals this is the self-lookup path rather than nextcloud_get_user or nextcloud_get_user_quota, which is a useful hint. However, there is no explicit when-to-use/when-not guidance or named alternative, so an agent facing both get_user_info and get_user must deduce the routing rule itself.

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