Retrieve details for a Confluence space by providing its space key, so you can inspect space configuration and metadata before managing pages or permissions.
Get space details
| Name | Required | Description | Default |
|---|---|---|---|
| spaceKey | Yes |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered structurally. The description adds nothing beyond that - no note on whether a missing space errors or returns empty, no auth/prerequisite context, despite openWorldHint implying network access.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three words with no filler and the resource is front-loaded after the verb. However, this is terseness rather than effective conciseness - the brevity comes at the cost of nearly all useful information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is trivial (one required param, no output schema, annotations present), so the bar is low, but the description still omits the spaceKey format and any sense of what the returned "details" comprise. It is minimally sufficient for an agent that already knows Confluence conventions, and thin for one that does not.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so spaceKey is an undocumented string in both the schema and the description. The description does not explain what a space key looks like (name vs. identifier) or give an example, which is exactly the gap it should fill for a single required parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
"Get space details" states a verb (get) and a resource (space), so the basic action is clear. But "details" is vague about what is returned, and nothing distinguishes it from the sibling conf_get_spaces (plural) or conf_get_page, which an agent must disambiguate on its own.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance at all. With a near-identical sibling (conf_get_spaces) in the toolset, the description never says when to fetch a single space versus list all spaces, leaving the agent to infer from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.