Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

atlassian-mcp__confluence_search

Read-only

Search Confluence content using CQL (Confluence Query Language). Returns matching pages/content with id, title, version, and link.

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": {
      "cql": "<cql>"
    },
    "name": "atlassian-mcp__confluence_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
cqlYesCQL query string (e.g. 'type=page AND space=ENG AND title~"onboarding"').
limitNoMaximum number of results to return (default 25).
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes the safety profile. The description adds useful beyond-schema context by enumerating the returned fields, which matters because no output schema exists. It does not say whether the limited result set is paginated or what happens when the CQL is malformed.

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?

Two short sentences, front-loaded with the mechanism and followed immediately by what you get back, with no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with no output schema, listing the returned fields is the right instinct, and the account and limit parameters are covered in schema. The omission of pagination and error behavior around an arbitrary query language leaves a meaningful gap.

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%, so all three parameters, including the CQL example and the account routing, are already documented. The description adds no meaning beyond that baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Search Confluence content') and names the query language (CQL), so an agent knows exactly what this does and what it returns (id, title, version, link). It does not, however, distinguish itself from sibling tools like confluence_list_pages or confluence_get_page, which is why it falls short of a 5.

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?

There is no guidance on when to reach for this instead of confluence_list_pages (a simple listing) or confluence_get_page (a single fetch). The mention of CQL implies that the caller must already know how to write a query, but the description never states that as a prerequisite or offers any alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DataToRAG toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources