Skip to main content
Glama

jira_get_fields

Retrieve all available field information including custom fields, showing IDs, names, and types for Jira instance configuration and integration.

Instructions

Get all available fields including custom fields - shows field IDs, names, and types

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'jira_get_fields' that invokes jiraClient.getFields() and returns the fields as JSON string.
    case "jira_get_fields": {
      const fields = await jiraClient.getFields();
      return {
        content: [{ type: "text", text: JSON.stringify(fields, null, 2) }],
      };
    }
  • src/index.ts:520-528 (registration)
    Tool registration in ListTools handler, including name, description, and empty input schema (no parameters required).
    {
      name: "jira_get_fields",
      description:
        "Get all available fields including custom fields - shows field IDs, names, and types",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Core implementation of getFields() in JiraClient class, which makes an API request to Jira's /field endpoint to fetch all available fields.
    // Get all fields (including custom fields)
    async getFields(): Promise<
      Array<{
        id: string;
        name: string;
        custom: boolean;
        schema?: { type: string };
      }>
    > {
      return this.request<
        Array<{
          id: string;
          name: string;
          custom: boolean;
          schema?: { type: string };
        }>
      >("/field");
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions what data is returned but lacks details on permissions required, rate limits, pagination, or error handling. For a read operation in a Jira context, this omission leaves significant gaps in understanding how the tool behaves.

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, efficient sentence that front-loads the key action and details without any wasted words. It directly communicates the tool's purpose and output, making it easy to parse and understand quickly.

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

Completeness3/5

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

Given the tool has no parameters and no output schema, the description adequately covers the basic purpose and output details. However, it lacks context on behavioral aspects like authentication needs or integration with other tools, which could be important in a Jira environment. It meets minimum viability but has clear gaps.

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 has 0 parameters, and the input schema has 100% description coverage (though empty). The description does not need to add parameter details, so it appropriately focuses on the tool's function. A baseline of 4 is applied as it compensates for the lack of parameters by clearly explaining the output scope.

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 clearly states the action ('Get all available fields') and specifies the resource ('fields including custom fields'), with details on what information is returned ('field IDs, names, and types'). It distinguishes from siblings like 'jira_get_field_options' by focusing on field metadata rather than options, though it could be more explicit about this distinction.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, such as 'jira_get_edit_meta' or 'jira_get_create_meta', which might also provide field information in specific contexts. There is no mention of prerequisites, timing, or exclusions, leaving usage unclear beyond the basic purpose.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yogeshhrathod/JiraMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server