Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List stacks

nextcloud_list_stacks
Read-onlyIdempotent

List the stacks (columns) of a Nextcloud Deck board by board ID, returning each column with its cards so you can inspect board structure and card distribution.

Instructions

List the stacks (columns) of one board, each with its cards.

GET /index.php/apps/deck/api/v1.0/boards/{board_id}/stacks

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": {
      "board_id": "<board_id>"
    },
    "name": "nextcloud_list_stacks"
  }
}

Input Schema

NameRequiredDescriptionDefault
board_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, idempotentHint, non-destructive, and openWorld, so the safety profile is covered. The description adds genuinely useful context by stating each stack is returned with its cards, implying a potentially large nested payload, but says nothing about ordering, pagination, or result size limits.

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?

Front-loaded single sentence stating what is returned, followed by the raw endpoint for reference. There is no filler, though the raw HTTP path is marginally useful to an agent compared to the descriptive sentence.

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 read-only list operation with annotations covering safety and no output schema, the description covers the essentials of what is returned. It is still thin on where board_id comes from and on result shape beyond 'each with its cards', which matters for a tool that nests cards under stacks.

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% for the single board_id parameter, so the description must carry the load. The embedded path template ({board_id}) confirms it is a board identifier used in the URL, but it does not state the format or that ids come from nextcloud_list_boards.

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 gives a specific verb and resource ('List the stacks (columns) of one board') and clarifies that cards are included in the result, which distinguishes it from nextcloud_list_boards and nextcloud_get_board. It stops short of naming those siblings explicitly, so an agent must infer the boundary itself.

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 phrase 'of one board' implies the tool is scoped to a single board and that a board_id is a prerequisite, but there is no explicit when-to-use guidance, no mention of using nextcloud_list_boards first to obtain an id, and no stated alternatives.

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