Skip to main content
Glama
vish288

mcp-atlassian-extended

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Confluence Get Time Off

confluence_get_time_off
Read-onlyIdempotent

Retrieve time-off events across all leave calendars for a date range; filter by person or calendar and see who is out on a specific day.

Instructions

Get time-off events for a date range across all leave calendars.

Pass person for one person's events, or a single day for start_date and end_date to see who is out on that day.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
personNoReturn only this person's events (exact, case-insensitive name match)
end_dateYesEnd date (YYYY-MM-DD, 'today', '+14d', etc.)
start_dateYesStart date (YYYY-MM-DD, 'today', '+14d', etc.)
calendar_nameNoFilter by calendar name
group_by_personNoGroup results by person

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.1
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Changed1 schema field changedv0.10.1
    • addedInput schema / properties / person
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Return only this person's events (exact, case-insensitive name match)"
+}
  3. First observedv0.6.13

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true and openWorld=true, so the safety profile is covered. The description adds that results span all leave calendars and that a single-day query returns 'who is out', but says nothing about result ordering, volume, or grouping behavior.

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 short sentences, front-loaded with the core purpose, then the two usage patterns. No filler, no restatement of the tool name.

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

Completeness4/5

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

No output schema exists, yet the description gives enough to call the tool correctly (required date range, optional person, implied grouping). It is slightly thin on what the returned events look like, but nothing essential to invocation 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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine semantic value beyond it: it explains that 'person' narrows to one individual's events and that setting start_date=end_date produces a single-day 'who is out' view, which the schema does not convey.

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 ('Get time-off events') plus scope ('across all leave calendars'), which separates it from the sibling confluence_list_calendars. It stops short of explicitly naming that sibling as the alternative, but the resource 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 Guidelines4/5

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

It gives two concrete calling patterns: pass 'person' for an individual, or equal start/end dates to see who is out on one day. That is clear context for invocation, though it notes no exclusions or prerequisites (e.g., what happens with no person filter).

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