Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Send message

nextcloud_send_message

Sends a single chat message to a specified Nextcloud conversation, with optional silent delivery and reply threading.

Instructions

Post one chat message to a conversation.

POST /ocs/v2.php/apps/spreed/api/v1/chat/{token}

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>",
      "message": "<message>"
    },
    "name": "nextcloud_send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
silentNo
messageYes
reply_toNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds essentially nothing beyond a raw endpoint: it does not explain what 'silent' does, how replies behave, whether messages can be edited/recalled, or what side effects occur.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short and front-loaded with the core purpose, but the second line is a bare REST endpoint that offers little to an agent beyond the openWorldHint annotation. Nothing is verbose, but the content is thin rather than tight.

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

Completeness2/5

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

For a mutation tool with four parameters at 0% schema coverage and no output schema, the description is too sparse. It should at minimum explain 'silent', 'reply_to', the token's meaning, and the expected result of posting a message.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden, yet it explains none of the four parameters. 'silent' and 'reply_to' are entirely opaque, and 'token' is only hinted at by the {token} URL fragment. This leaves most parameters undocumented in both places.

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 ('Post one chat message to a conversation'), clearly distinguishing it from siblings like nextcloud_list_messages and nextcloud_delete_message. It does not explicitly name alternatives, but the verb+resource pairing is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus nextcloud_list_messages, nextcloud_create_conversation, or other messaging siblings, nor any prerequisites such as joining the conversation or required permissions.

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