Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get share

nextcloud_get_share
Read-onlyIdempotent

Retrieve one Nextcloud share's details by share ID to review its recipients, permissions, and link settings.

Instructions

Read one share by id.

GET /ocs/v2.php/apps/files_sharing/api/v1/shares/{share_id}

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": {
      "share_id": "<share_id>"
    },
    "name": "nextcloud_get_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
share_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the concrete OCS v2 REST path as provenance and does not mention permission requirements, 404/not-found behavior, or what the returned share contains.

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 with the core action front-loaded; no filler. The embedded HTTP endpoint is marginally useful to an agent and is brief enough not to be wasteful, though it is closer to implementation detail than invocation guidance.

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 single-parameter read tool whose annotations cover safety and idempotency, the definition is adequate to invoke correctly. However, with no output schema present, it gives no sense of the returned share payload (path, permissions, expiry, recipients) or error conditions, which an agent would want for planning.

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?

Schema description coverage is 0%, so the description carries the burden, but 'by id' largely restates the parameter name share_id. It confirms the argument identifies an existing share rather than a user or file, yet gives no format hint (numeric OCS share id vs. token) to help an agent supply a valid value.

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 one share by id') and adds the underlying OCS endpoint, so it is unambiguous that this fetches a single share object. It implicitly contrasts with nextcloud_list_shares (plural, collection) via 'one share', though it never names that sibling.

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: the agent can infer 'use this when you already have a share_id' versus nextcloud_list_shares for discovery, but no explicit when-to-use or when-not-to-use guidance is given. Nothing is said about needing permissions or what happens for an invalid/unknown share id.

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