Skip to main content
Glama

ticket_lint

Read-onlyIdempotent

Full Jira-ticket quality linter (whole ticket, not just AC - use acceptance_criteria_validator for the deep AC pass). POST one ticket or a batch (max 50) and get per-ticket findings with severity + concrete fixes: missing/weak summary or description, missing AC or estimate, bugs without repro/expected-vs-actual/environment, missing epic link, points-vs-hours mismatch, oversized estimates to split, urgent-but-thin tickets. Returns score, grade, and a ready/needs_work verdict per ticket plus batch summary. Type-aware rules (story/bug/task/epic/subtask), strict profile available. Deterministic, no LLM.

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": "ticket_lint"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticketNoOne Jira-style ticket. Missing fields ARE findings, so send what you have.
profileNoDefault "normal" (ready at 75). "strict" bumps severities and needs 85.
ticketsNoAlternative: batch of up to 50 tickets. Send ticket or tickets, not both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / profile / description
      Added value: +"Default \"normal\" (ready at 75). \"strict\" bumps severities and needs 85."
    • changedInput schema / properties / ticket / description
      Previous value: -"One ticket: {key, summary, description, acceptance_criteria, issue_type, estimate_hours|story_points, priority, labels, components, epic_link, ...}. Missing fields ARE findings."New value: +"One Jira-style ticket. Missing fields ARE findings, so send what you have."
    • addedInput schema / properties / ticket / properties
      Added value: +{
      +  "acceptance_criteria": {
      +    "description": "A list, or one string with one criterion per line.",
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": [
      +      "string",
      +      "array"
      +    ]
      +  },
      +  "assignee": {
      +    "description": "Owner, if assigned.",
      +    "type": "string"
      +  },
      +  "attachments_count": {
      +    "description": "Number of attachments; 0 on a bug is flagged.",
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  "components": {
      +    "description": "Components touched.",
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  "description": {
      +    "description": "The ticket body.",
      +    "type": "string"
      +  },
      +  "epic_link": {
      +    "description": "Parent epic key.",
      +    "type": "string"
      +  },
      +  "estimate_hours": {
      +    "description": "Estimate in hours.",
      +    "type": "number"
      +  },
      +  "issue_type": {
      +    "description": "story, bug, task, epic or subtask; anything else is linted as a task.",
      +    "type": "string"
      +  },
      +  "key": {
      +    "description": "Ticket key, echoed back, e.g. \"PROJ-123\".",
      +    "type": "string"
      +  },
      +  "labels": {
      +    "description": "Labels.",
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  "priority": {
      +    "description": "e.g. \"High\". highest/blocker with a thin description is flagged.",
      +    "type": "string"
      +  },
      +  "story_points": {
      +    "description": "Estimate in points; cross-checked against estimate_hours.",
      +    "type": "number"
      +  },
      +  "summary": {
      +    "description": "The one-line title.",
      +    "type": "string"
      +  }
      +}
    • changedInput schema / properties / tickets / description
      Previous value: -"Alternative: batch of up to 50 tickets."New value: +"Alternative: batch of up to 50 tickets. Send ticket or tickets, not both."
    • addedInput schema / properties / tickets / items / additionalProperties
      Added value: +{
      +  "description": "See ticket."
      +}
    • addedInput schema / properties / tickets / items / description
      Added value: +"Same fields as ticket."
    • addedInput schema / properties / tickets / maxItems
      Added value: +50
    • addedInput schema / properties / tickets / minItems
      Added value: +1
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral context on top: per-ticket findings with severity plus concrete fixes, a score/grade/ready-vs-needs_work verdict, batch summary, type-aware rule sets for story/bug/task/epic/subtask, the two profiles and their thresholds, and the fact that it is deterministic with no LLM involved. The only friction is the phrase "POST one ticket," which is transport phrasing for an operation annotated as a read, though it is not a substantive contradiction.

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?

Front-loaded with purpose and the sibling disambiguation before the feature list, and nearly every clause carries distinct information (findings, verdict, profiles, determinism). It is a dense single paragraph with a nested parenthetical and a long comma-listed set of rule categories, which costs a little scanability.

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?

No output schema exists, and the description compensates by describing the return shape (per-ticket severity findings with fixes, score, grade, ready/needs_work verdict, batch summary). Combined with the profile thresholds, batch cap, and determinism statement, an agent has everything needed to call it and interpret results.

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%, so the baseline applies: the schema already documents ticket fields, the profile enum with its 75/85 thresholds, and the max-50 batch limit. The description largely restates those facts ("batch (max 50)," "strict profile available") rather than adding new meaning, though "type-aware rules (story/bug/task/epic/subtask)" gives useful intent for issue_type.

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 ("Full Jira-ticket quality linter") plus an explicit scope boundary: the whole ticket, not just acceptance criteria. It names the sibling it is not (acceptance_criteria_validator for the deep AC pass) and enumerates the concrete defect classes it detects, so an agent can tell it apart from story_lint, defect_triage, or estimate_sanity without opening the schema.

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 a clear routing rule against one sibling ("use acceptance_criteria_validator for the deep AC pass") and describes both input modes (single ticket vs. batch up to 50). It does not address overlap with other plausible siblings such as story_lint, defect_triage, or estimate_sanity, and gives no explicit when-not-to-use condition beyond that single alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.