Skip to main content
Glama

jira_get_fields

Lists Jira fields, including system and custom fields, with IDs, names, JQL clause names, and searchability. Use it to look up the correct JQL clause name.

Instructions

List the Jira instance field catalog (system fields like Summary plus every custom field). Returns field IDs, names, clauseNames for JQL, and whether they're searchable. Use this to look up a JQL clause name. For fields on an issue type, use jira_get_edit_meta or jira_get_create_meta instead — do not call this before every create/update.

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

Input Schema

NameRequiredDescriptionDefault
customOnlyNoSet to true to only return fields whose id is customfield_<digits>

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden and does well by describing the response payload (IDs, names, clauseNames, searchability) for a tool that has no output schema. It omits operational details such as whether the catalog is cached, permission requirements, or size/pagination behavior, which keeps it short of a 5.

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?

Three tight sentences, front-loaded with the purpose, then the return shape, then the routing/negative guidance. No filler or redundant restatement of the tool name.

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

Completeness5/5

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

For a read-only single-parameter catalog tool with no output schema, the description covers purpose, payload contents, and sibling routing, which is everything an agent needs to select and call it correctly. The absence of auth/pagination notes is not material at this complexity level.

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% and the single customOnly parameter is fully documented in the schema, so the baseline is 3. The description hints at the custom-vs-system split but never references the parameter or how to filter, adding no syntax or semantics beyond the schema.

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

Purpose5/5

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

States a specific verb and resource ('List the Jira instance field catalog') and enumerates what the catalog contains, including the distinction between system fields like Summary and custom fields. It also summarizes the returned attributes (field IDs, names, clauseNames, searchable flag), so an agent knows exactly what resource it is fetching.

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

Usage Guidelines5/5

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

Gives an explicit positive use case ('Use this to look up a JQL clause name'), names two concrete alternatives (jira_get_edit_meta, jira_get_create_meta) with the condition that selects them, and adds a negative guardrail ('do not call this before every create/update') that prevents an obvious misuse pattern.

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