Skip to main content
Glama

Lint acceptance criteria

lint_acceptance_criteria
Read-onlyIdempotent

Validates acceptance criteria against task-type rules, flagging incomplete or out-of-order Given/When/Then steps, vague terms, unitless numbers, and format issues with line-level hints.

Instructions

Check acceptance criteria against the rules of their task type: Given/When/Then complete and in order, observable Then steps, vague words, numbers without units, required fields and formats. Pass the text as it is in the ticket plus ticket_type and labels (or type). Every finding has line, column, rule and a hint; template://{type} shows the expected form. Deterministic and read-only; it does not rewrite the text.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "lint_acceptance_criteria"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe acceptance criteria as they are in the ticket
typeNoTask type (file name in dod/ without .yaml); usually leave it out and pass ticket_type and labels
labelsNoLabels of the ticket, as they are
ticket_typeNoTicket or work item type as in the ticket, e.g. "Story"

Output Schema

NameRequiredDescriptionDefault
typeYes
limitsYes
summaryYes
findingsYes
truncatedYes
resolutionYes
dod_versionYes
rules_appliedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Deterministic and read-only; it does not rewrite the text' mostly restates the safety profile. It earns credit for the non-obvious operational detail that findings point to 'template://{type}' for the expected form, which tells the agent how to act on failures.

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?

Two dense sentences, front-loaded with purpose then rules then calling convention then output shape; the rule enumeration is compressed into a list-like clause rather than expanded prose. The closing 'every finding has line, column, rule and a hint' is partly redundant given an output schema exists, a minor waste.

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?

An output schema exists, so the description is not obligated to explain return values, and it correctly stops at noting findings carry line/column/rule/hint. It covers determinism, the no-rewrite guarantee and the template remediation path — what is missing is only guidance on alternatives or failure conditions.

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?

With 100% schema description coverage the baseline is 3, and the schema already carries the key routing advice ('usually leave it out and pass ticket_type and labels'). The description reinforces that with '(or type)' and stresses verbatim text ('as it is in the ticket'), but adds no format, precedence or fallback detail the schema lacks.

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 definition opens with a specific verb and resource ('Check acceptance criteria') and immediately scopes it by enumerating the rule families applied (Given/When/Then order, observable Thens, vague words, units, required fields). That is enough for an agent to tell it apart from the DoD-oriented siblings (check_dod, diff_dod, get_dod) without opening any schema.

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?

It gives concrete input guidance ('Pass the text as it is in the ticket plus ticket_type and labels (or type)'), which tells the agent how to call it well. It stops short of any explicit when-to-use / when-not-to-use statement or any comparison to a sibling, so usage is implied rather than routed.

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

Deploy Server

Other Tools