Skip to main content
Glama

jira_get_projects

List all Jira projects the authenticated user can access, returning project keys, names, and lead details so you can discover available projects before searching issues or creating new ones.

Instructions

List all Jira projects the authenticated user has access to. Returns project keys, names, and lead information. Use this to discover available projects before searching for issues or creating new ones. If JIRA_PROJECTS_FILTER environment variable is set, only those specific projects are returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jira_get_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the access scoping (only projects the authenticated user can see), the shape of returned data (keys, names, lead info), and a non-obvious environment-variable filter that silently narrows results. It omits pagination or result-size behavior for what could be a large list, which is the main remaining gap.

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?

Four short sentences, each carrying distinct information: purpose, return contents, usage context, and the env-var caveat. Purpose is front-loaded and nothing is redundant.

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 zero-parameter read tool with no output schema, the description supplies return-field information, access scoping, and the configuration-based filter — enough to call it correctly. The only omission is what happens with large result sets or whether results are paginated.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly does not invent a parameter list.

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?

States a specific verb and resource ('List all Jira projects') plus the scope ('the authenticated user has access to'), which clearly separates it from the singular jira_get_project sibling. It stops just short of naming that sibling explicitly, so an agent infers the distinction from 'all' versus a single-project lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives concrete when-to-use guidance: 'discover available projects before searching for issues or creating new ones.' This positions it as a prerequisite step for downstream actions. No explicit when-not-to-use or named alternative is given, so it falls short of a 5.

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