Skip to main content
Glama
Sign In
dev.mcp

dev.mcp

by iwilldotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

jira_search_jql

Search Jira issues with JQL queries. Use JQL to filter, select fields, expand details, limit results, and paginate for targeted issue retrieval.

Instructions

Search issues with JQL (POST /rest/api/3/search/jql).

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": "jira_search_jql"
  }
}

Input Schema

NameRequiredDescriptionDefault
jqlYes
expandNo
fieldsNo
maxResultsNo
nextPageTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior on its own. It only repeats the search action and the POST endpoint; it does not mention pagination, response shape, authentication needs, or whether the operation has side effects.

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, front-loaded sentence with no filler. The endpoint parenthetical adds useful API context and every word earns its place.

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?

For a tool with 5 parameters, no parameter descriptions, no annotations, and no output schema, this description is under-specified. It does not explain pagination via nextPageToken, how fields and expand work, or what the response contains.

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

Parameters2/5

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

Schema description coverage is 0%, yet the description only clarifies the jql parameter by mentioning JQL. The parameters expand, fields, maxResults, and nextPageToken receive no explanation beyond their names in the schema.

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 issues with JQL' and gives the exact REST endpoint. It is clearly distinct from jira_get_issue, which retrieves a single issue, though it does not explicitly name alternatives.

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?

The phrase 'Search issues with JQL' implies the tool is for JQL-based issue searching, but it does not state when to prefer it over jira_get_issue or other Jira tools. There is no explicit when-to-use or exclusion guidance.

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