Skip to main content
Glama
Sign In
MCP Atlassian Server

MCP Atlassian Server

by dunz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_confluence_space

Retrieve details of a Confluence space by its key, including name, type, status, and description.

Instructions

Get details of a specific Confluence space by its key. Returns space information including name, type, status, and description.

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": {
      "spaceKey": "<spaceKey>"
    },
    "name": "get_confluence_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
expandNoProperties to expand in the response (e.g., "description.plain,homepage").description.plain,homepage
spaceKeyYesThe key of the space to retrieve (e.g., "DEV").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A4/5.0
Behavior3/5

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

There are no annotations, so the description must carry the behavioral burden. It accurately indicates a read operation and previews the returned fields, but it doesn't state explicitly that the operation is read-only/no side effects or what happens on an invalid key or with the expand parameter. This is adequate but not rich.

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?

A single, well-structured sentence that front-loads the action and resource, then adds useful return-field detail. No filler or repetition.

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?

For a simple retrieval tool with two fully described parameters and no output schema, the description provides enough for an agent to make the call. Minor gaps are error/not-found behavior and the effect of expand, but the schema covers expand.

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 100%: both spaceKey and expand are already well documented in the schema. The description's 'by its key' paraphrases spaceKey but adds no additional semantic value beyond the schema.

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 uses a specific verb ('Get details') and a precise resource ('a specific Confluence space'), scoped by the space key. This clearly differentiates it from list_confluence_spaces, which retrieves multiple spaces.

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?

The phrase 'a specific Confluence space by its key' establishes the clear context: use this when you already know the key and need a single space. It doesn't explicitly point to list_confluence_spaces for enumeration, so it stops short of full when/when-not guidance.

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