Skip to main content
Glama

Check an item against its Definition of Done

check_dod
Read-onlyIdempotent

Checks collected evidence against an item's Definition of Done and returns met, not met, or needs-judgment results with findings and hints for missing or stale evidence.

Instructions

Check the evidence you collected for an item against its DoD. For every evidence criterion, fetch the value with the tool named in get_dod and pass it unchanged: criterion, source, tool, arguments, retrieved_at (ISO 8601 with time zone), raw and, for commits, ref. Never invent or retype values; leave out what you could not fetch. Returns met / not_met / needs_judgment per criterion with findings (evidence_missing, evidence_stale, evidence_other_ref …) and a hint on how to get missing evidence. There is no overall status: the team decides whether the item is done. Read-only; writes nothing to the ticket.

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": {
      "item": "<item>"
    },
    "name": "check_dod"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
as_ofNoReference time for the age of evidence (ISO 8601); default: now
evidenceNo

Output Schema

NameRequiredDescriptionDefault
itemYes
typeYes
as_ofYes
limitsYes
summaryYes
criteriaYes
decisionYes
resolutionYes
dod_versionYes
unused_evidenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses that there is no overall status, that the team decides whether the item is done, and that results include met / not_met / needs_judgment with findings and hints. It also explicitly says it writes nothing to the ticket, which is useful behavioral context even with annotations present.

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 dense but appropriately front-loaded for a tool with nested evidence objects and strict data-integrity rules. Every sentence contributes operational guidance or clarifies the result semantics.

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 the complex nested input schema, annotations, and existing output schema, the description provides enough context to use the tool correctly. It explains evidence collection, required fidelity, result statuses, and the absence of an overall status, without needing to restate return-schema details.

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?

Although schema description coverage is only 33%, the description adds meaningful semantics for the evidence parameters: use the tool named in get_dod, pass values unchanged, include ISO 8601 retrieved_at with time zone, and include ref for commits. It does not explain every item field, but it compensates for the most important evidence-shape requirements.

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 states a specific verb and resource: checking collected evidence for an item against its Definition of Done. It clearly explains the per-criterion output, but it does not explicitly differentiate this tool from siblings such as diff_dod or lint_acceptance_criteria.

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?

It gives clear workflow guidance: fetch each evidence value with the tool named in get_dod and pass it unchanged, and leave out anything that could not be fetched. It lacks explicit when-not-to-use guidance or direct comparison with alternative DoD tools.

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