Confluence Communication Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_cql_searchC | Execute a CQL query on Confluence to search pages |
| get_page_contentB | Get the content of a Confluence page |
| update_page_contentC | Update the content of a Confluence page |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: execute_cql_search handles search queries, get_page_content retrieves page content, and update_page_content modifies page content. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun pattern (execute_cql_search, get_page_content, update_page_content) with clear action verbs and descriptive nouns. This uniformity enhances readability and predictability across the tool set.
With only 3 tools, the set feels thin for a Confluence server, lacking operations like creating or deleting pages, managing comments, or handling attachments. While the tools cover basic read/update/search, the scope is limited and may require workarounds for full domain coverage.
The tool set is significantly incomplete for Confluence communication, missing essential CRUD operations such as create_page and delete_page, as well as functionalities for comments, spaces, or user management. This will likely cause agent failures when attempting comprehensive workflows.