Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

List agile boards

jira_list_boards
Read-only

List Jira Software Scrum and Kanban boards, optionally filtered by project key or board name, to help identify boards for reporting or issue management.

Instructions

List Jira Software boards (Scrum/Kanban), optionally filtered by project or name.

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_list_boards"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
instanceNoJira instance name (see jira_list_instances). Optional: calls are routed automatically by 'name:KEY' prefixes, issue URLs, project-key mapping, the default instance, or when only one instance exists.
maxResultsNo
projectKeyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only that boards are Scrum/Kanban types; it says nothing about result ordering, pagination behavior, or what happens when a filter matches nothing, which are the behavioral facts an agent would still need.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity borders on under-specification rather than tightness.

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 list tool with no output schema and 25% parameter coverage, the description should at minimum convey the result shape or pagination contract. It leaves the agent guessing about what a board record contains and how to page through more than maxResults entries.

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 coverage is only 25% — just the 'instance' parameter is documented in the schema. The description names 'project' and 'name' as filters but does not explain matching semantics (exact vs. substring), and it never addresses maxResults or the 100-item cap, so it does not compensate for the coverage gap.

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 Jira Software boards') and narrows it with '(Scrum/Kanban)', so the agent knows exactly what entity is returned. It does not explicitly contrast itself with siblings like jira_list_sprints or jira_list_projects, but the resource noun is distinctive enough to separate it.

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?

'Optionally filtered by project or name' implies when the filters are useful, but there is no explicit when-to-use guidance, no mention of paging through results with maxResults, and no stated alternative for retrieving boards by other criteria. Usage is inferable rather than stated.

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