Skip to main content
Glama

Get the Definition of Done

get_dod
Read-onlyIdempotent

Retrieve Definition of Done criteria for a ticket type and labels, including evidence sources, judgment questions, and attestation requirements, or list available task types.

Instructions

The Definition of Done for a ticket: pass ticket_type and labels as they are in the ticket (or type explicitly). Returns every criterion of base and type with its origin and check kind: evidence (which source and tool deliver it, what value is expected, how old it may be), judgment (a question you answer with rubric://dod/{type}) or attestation (a role confirms). Without arguments: the list of task types. An ambiguous or unknown type is an error with a hint, never a default. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
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
dodNo
overviewNo
resolutionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the safety profile is inherited. The description adds genuinely new behavioral context beyond them: the three check kinds (evidence, judgment, attestation), what evidence criteria carry, the rubric:// URI for judgment, and the error-with-hint behavior for unknown types.

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?

Purpose is front-loaded in the first clause, then parameter guidance, return shape, and error behavior follow in a logical order. It is dense but nearly every clause carries information; the parenthetical rubric://dod/{type} is the only slightly cryptic fragment.

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?

For a zero-required-parameter read tool with an output schema and full annotation coverage, the description covers invocation, the no-argument fallback, return semantics, and error behavior. An output schema exists so return fields needn't be spelled out further; the remaining gap is only the absence of explicit sibling routing.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns above that by explaining the relationship between the parameters: type is a dod/ file name that should usually be omitted in favor of ticket_type plus labels, and the no-argument case has a defined meaning. This resolves real ambiguity about which of the three optional parameters to supply.

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 names a specific resource (the Definition of Done for a ticket) and states what is returned: every base and type criterion with origin and check kind. It implicitly distinguishes this retrieval tool from check/diff siblings through 'Read-only' and the return-oriented framing, though it never names an alternative explicitly.

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 concrete invocation guidance: pass ticket_type and labels as they appear on the ticket, or pass type explicitly, and with no arguments it returns the list of task types. It also sets an error policy (ambiguous/unknown type errors with a hint, never a default). What is missing is any explicit statement of when to prefer check_dod or diff_dod instead.

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