nc-mcp-server

close_poll

DestructiveIdempotent

Close a poll in a Nextcloud Talk conversation to stop voting and reveal final results to all participants. Irreversible action for poll creators or moderators.

Instructions

Close a poll in a Talk conversation.

Once closed, no more votes can be cast and results become visible to all participants (regardless of result_mode). Only the poll creator or a conversation moderator can close a poll.

This action is irreversible — a closed poll cannot be reopened.

Args: token: The conversation token. poll_id: The poll ID to close.

Returns: JSON object with the final poll results including all votes and details.

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": {
      "token": "<token>",
      "poll_id": "<poll_id>"
    },
    "name": "close_poll"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes
`poll_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the destructiveHint and idempotentHint annotations, the description explains irreversibility, that voting stops, that results become visible regardless of result_mode, and the required authorization. No contradiction with annotations exists.

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?

The description is tightly organized: one-sentence purpose, behavioral consequences, permission/irreversibility warning, then args and return. Every sentence adds relevant information with no filler.

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

Completeness5/5

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

For a two-parameter mutating tool, the description covers authorization, side effects, irreversibility, and return shape. The output schema signal reduces the need to document return values further, and nothing critical is missing.

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?

Although schema description coverage is 0%, the Args section adds plain-language meaning: token is the conversation token and poll_id is the poll to close. It does not go into lookup/origin details, but it compensates for the bare schema titles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Close a poll in a Talk conversation') and distinguishes this from sibling poll operations like create_poll and vote_poll. It also explains the consequences of closing, making the tool's role unambiguous.

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 clearly communicates when to use it (to end a poll and reveal results) and adds a permission constraint (creator/moderator only). It does not explicitly name alternatives or say 'use X instead', but the context is sufficiently clear.

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

Deploy Server