Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

atlassian-mcp__jira_search

Read-only

Search Jira issues using JQL (Jira Query Language). Returns matching issues with key fields. Supports pagination via next_page_token.

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": {
      "jql": "<jql>"
    },
    "name": "atlassian-mcp__jira_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
jqlYesJQL query string (e.g. 'project = PROJ AND status = Open')
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
max_resultsNoMaximum number of results per page (default 50)
next_page_tokenNoPagination token from a previous search response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered and the bar is lower. The description adds the return shape at a high level and that paging is token-based, but says nothing about default page size, result caps, permission scope, or JQL syntax failures.

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?

Three short sentences, front-loaded with the purpose, then return behavior, then pagination. Nothing is wasted, though it is terse enough to omit useful caveats.

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

Completeness4/5

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

For a read-only search tool with a fully documented four-parameter schema and no output schema, the description covers purpose, return nature, and pagination. The main residual gap is that it does not enumerate which 'key fields' are returned, forcing the agent to inspect results.

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%, including the JQL example, account selection, max_results default of 50, and the pagination token, so the schema carries the parameter burden. The description only echoes the next_page_token behavior, adding no new syntax or constraint information.

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 states a specific verb and resource ('Search Jira issues') plus the query dialect (JQL) and what comes back ('matching issues with key fields'). It is clearly distinct from jira_get_issue in practice, but it never names the sibling or explains the split, so 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 Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for JQL-based lookup rather than single-issue retrieval, and the pagination sentence hints at iterative calls. There is no explicit when-to-use versus jira_get_issue or when-not guidance.

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