Skip to main content
Glama
Sign In
dev.mcp

dev.mcp

by iwilldotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

confluence_get_spaces

Retrieve a list of Confluence spaces by key or type. Use this tool to explore available spaces and paginate through results for content discovery.

Instructions

Lists spaces (GET /wiki/api/v2/spaces).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "confluence_get_spaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysNoCSV keys, e.g. ENG,DOC.
typeNo
limitNo
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

There are no annotations, so the description carries the full behavioral disclosure burden. It implies a read-only operation via GET, but does not mention pagination, response shape, scope of accessible spaces, or authentication requirements.

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?

The description is a single concise sentence with no filler. Including the endpoint adds precision without unnecessary length, making it well-structured for a simple list operation.

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?

With no output schema and no annotations, 'Lists spaces' plus the endpoint is too thin. An agent cannot tell what the response looks like, how pagination works, or how the optional parameters affect behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%: keys is described, but type, limit, and cursor are not. The description itself adds no parameter meaning, so it fails to compensate for the low schema coverage.

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 identifies a specific verb ('Lists') and resource ('spaces'), and includes the REST endpoint (GET /wiki/api/v2/spaces). This clearly distinguishes it from sibling tools like confluence_get_page or confluence_get_pages_in_space.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives such as confluence_search_cql or confluence_get_pages_in_space. The agent must infer appropriate usage from the tool name alone.

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