Skip to main content
Glama

Get calendar object

nextcloud_get_calendar_object
Read-onlyIdempotent

Retrieve a single calendar event or task by URL, returning parsed fields, ETag, and raw iCalendar text for inspection or synchronization.

Instructions

Read one event or task: its parsed fields, etag and raw iCalendar text.

GET /remote.php/dav/calendars/{user}/{calendar}/{object}.ics

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": {
      "object_url": "<object_url>"
    },
    "name": "nextcloud_get_calendar_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
object_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description goes beyond them by disclosing the shape of the payload (parsed fields, etag, raw iCalendar), which matters because there is no output schema. It stops short of covering error behavior for a missing or malformed object.

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?

Two lines, front-loaded with the action and return content, with the endpoint as supporting detail. No filler or redundant restatement of the title.

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 single-parameter read tool with no output schema, the description covers what is returned and its read-only nature. The unresolved gap is provenance of the only required parameter at 0% schema coverage, plus absent failure-mode guidance.

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?

The single required parameter has 0% schema description coverage, so the description must compensate. The DAV path template hints at the expected resource shape, but it does not clarify whether object_url is a full URL, a relative path, or an ID, nor how to obtain one.

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?

States a specific verb and resource ('Read one event or task') and enumerates what is returned ('parsed fields, etag and raw iCalendar text'), which distinguishes it from the list_events/list_tasks siblings that return collections. The DAV path template reinforces the singular-object scope.

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 singular framing implies it is the single-object counterpart to nextcloud_list_events, but no sibling or alternative is named and there is no statement of preconditions. Critically, nothing says where a valid object_url comes from, which is the main usage decision an agent faces.

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