Skip to main content
Glama

Get user quota

nextcloud_get_user_quota
Read-onlyIdempotent

Retrieve the connected Nextcloud account's storage quota to check used and available space.

Instructions

Read the storage quota of the connected account.

PROPFIND /remote.php/dav/files/{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_quota"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.4

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds only the underlying PROPFIND endpoint, which is implementation detail rather than agent-relevant behavior such as what happens on permission failure or whether quotas are cached. No return shape is described.

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 purpose; nothing redundant. The raw endpoint line is the only questionable element and is placed after the purpose statement rather than before it.

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

Completeness3/5

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

For a simple zero-parameter read, the description is close to sufficient, and annotations carry the safety profile. However, with no output schema, it never indicates what the quota response contains (used, total, available, percentage), leaving the agent to guess at the return value.

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

Parameters3/5

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

With zero parameters the baseline is 4, but the description's mention of the path template '/remote.php/dav/files/{user}' introduces a '{user}' token that is not a parameter in the schema, which could mislead an agent into thinking a user argument is required or accepted.

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: 'Read the storage quota of the connected account'. The 'connected account' scoping distinguishes it from sibling tools like nextcloud_get_user_info, which would return broader profile data.

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?

Usage is only implied by the phrase 'connected account', which suggests the tool cannot query arbitrary users' quotas. There is no explicit statement of when to prefer this over nextcloud_get_user or when it would fail (e.g. admin-only quotas).

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