Skip to main content
Glama
Sign In
Confluence MCP Server

Confluence MCP Server

by gkrauchunas-arlo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

confluence_get_space

Retrieve details of a Confluence space by providing its space key. Access space information like name, description, and permissions.

Instructions

Get information about a specific Confluence space

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": "confluence_get_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaceKeyYesThe key of the space to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only says 'Get information', failing to disclose behavioral traits like return format, authentication requirements, rate limits, or potential errors.

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?

The description is a single sentence that efficiently states the purpose. It is not verbose, but could include more detail without being wasteful.

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?

The tool has no output schema and no annotations, yet the description provides no hint about return values, pagination, or related data. This under-specifies the behavior for an agent.

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?

Input schema has 100% coverage for the single parameter 'spaceKey' with a description. The tool description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states 'Get information about a specific Confluence space', which uses a specific verb and resource, and distinguishes from sibling tools like 'list_spaces' (list vs. get specific) and 'get_page' (different resource).

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 implied: use when needing info on a specific space. There is no explicit guidance on when to use this vs. alternatives (e.g., 'list_spaces' for all spaces) or prerequisites, which leaves some ambiguity.

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