Skip to main content
Glama
Sign In
nextcloud-agent

nextcloud-agent

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get conversation

nextcloud_get_conversation
Read-onlyIdempotent

Retrieves one Nextcloud Talk conversation by its token so you can inspect room details for a specific conversation identifier.

Instructions

Read one conversation by its token.

GET /ocs/v2.php/apps/spreed/api/v4/room/{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>"
    },
    "name": "nextcloud_get_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only the raw REST endpoint (GET .../room/{token}), which hints at an HTTP-backed read but says nothing about permissions required, error behavior for an invalid token, or what room data comes back.

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 and no filler. The endpoint line is of limited use to an agent choosing a tool but it is compact and placed after the purpose statement.

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?

There is no output schema, so in principle the description should describe the return shape, and it does not — it never says the result is conversation/room metadata or participant state. Combined with zero parameter documentation and no permission or error context, the description is thinner than a single-record read tool warrants.

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 schema supplies only the type. The phrase 'by its token' confirms the parameter is a conversation token rather than a message or share token, which is a real but minimal semantic addition; format and source of the token remain undocumented.

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 states a specific verb and resource ('Read one conversation') and scopes it to a lookup by token, which is enough to separate it from nextcloud_list_conversations or nextcloud_list_messages. It does not explicitly name those siblings, so it stops short of full differentiation.

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: it is a single-record fetch, so an agent can infer 'use when you already have a conversation token.' There is no stated prerequisite (e.g. that the token comes from list_conversations) and no when-not-use guidance or named alternative.

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