Skip to main content
Glama
lfern

jira-gateway

by lfern
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Server Quality Checklist

58%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v0.1.0

  • Disambiguation5/5

    Each tool has a clearly distinct purpose: creating tasks, listing assigned tasks, and transitioning task status. No overlap exists.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: create_task, list_my_tasks, start_task.

    Tool Count4/5

    Three tools is a minimal but reasonable set for a Jira gateway focusing on task creation, listing, and status transitions.

    Completeness3/5

    Core create, read, and transition operations are covered, but missing update, delete, and advanced querying limit completeness for typical Jira workflows.

  • Average 4.5/5 across 3 of 3 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 6 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.

    If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.

    MCP servers without a LICENSE cannot be installed.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior4/5

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

    Clearly declares read-only behavior and that filter is fixed with no parameters. No annotations provided, so description carries burden well.

    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?

    Two concise sentences with no superfluous information; every word adds value.

    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?

    Given zero parameters and presence of output schema, description fully specifies scope and constraints (assigned, not closed, configured project, read-only).

    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?

    No parameters; description reinforces that no JQL or parameters are accepted, adding clarity beyond the empty 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?

    Description clearly states verb 'list' and resource 'tasks' with specific filter (assigned and not closed). Distinguishes from siblings by noting read-only and no parameters.

    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?

    Description indicates it is read-only with a fixed filter, implying when to use it (viewing tasks) vs. siblings (create/start). Could explicitly mention alternatives but context suffices.

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

  • Behavior4/5

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

    Discloses key behaviors: only works if issue assigned to user, returns error without changes otherwise, and states it does not touch git. With no annotations, description carries full burden and covers important 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?

    Concise Spanish description, front-loads the main action, no wasted sentences. Every sentence serves a purpose: action, parameter explanation, prerequisite, side-effect note.

    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?

    Complete for a Jira transition tool with moderate complexity. Covers default status, custom transitions, assignment requirement, and clarifies no git involvement. No output schema, but behavior is well explained.

    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?

    Specifies 'issue_key' is required and explains 'status': default to configured in-progress, or use a custom transition name. Adds meaning beyond schema (which has 0% coverage), though could mention expected format of 'issue_key'.

    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?

    The description clearly states it transitions an issue in Jira, specifying the default action (move to 'in progress') and the optional custom status. It distinguishes from siblings: 'create_task' (create) and 'list_my_tasks' (list).

    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?

    Provides clear context: use when starting work on an issue, with guidance on the 'status' parameter for pre-development steps. Implicitly excludes when not assigned (returns error) and mentions no git interaction, but no explicit when-not-to-use or alternatives.

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

  • Behavior5/5

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

    Al no haber anotaciones, la descripción asume la carga completa. Revela que la herramienta mueve automáticamente la tarea a un estado específico (JIRA_SELECTED_STATUS) y detalla el comportamiento del parámetro confirm (preview sin creación, ejecución con confirm=True).

    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?

    La descripción es breve (4 oraciones), con la información más importante al inicio. Cada oración aporta valor: propósito, comportamiento automático y el flujo de confirmación. No hay redundancia.

    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?

    Aunque falta un esquema de salida, la descripción cubre bien el comportamiento principal. Sin embargo, no menciona qué devuelve (por ejemplo, los detalles de la tarea creada) ni posibles errores o requisitos previos. Aun así, es suficiente para un uso básico.

    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?

    La cobertura de descripción del esquema es 0%. La descripción solo explica el parámetro confirm en detalle; los demás (summary, labels, issue_type, description) no se describen más allá de sus nombres. Aunque los nombres son autoexplicativos, la falta de aclaración reduce la puntuación.

    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?

    El verbo 'crear' y el recurso 'tarea' son específicos. La descripción indica claramente que crea una tarea en Jira en el proyecto configurado, lo que la distingue de los hermanos 'list_my_tasks' y 'start_task'.

    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?

    La descripción instruye explícitamente que primero se llame sin confirm (o con confirm=False) para obtener una vista previa, y solo si el usuario aprueba, se llame con confirm=True. Esto indica cuándo y cómo usar la herramienta de forma segura.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

jira-gateway-mcp MCP server

Copy to your README.md:

Score Badge

jira-gateway-mcp MCP server

Copy to your README.md:

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/lfern/jira-gateway-mcp'

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