Skip to main content
Glama

Compare two versions of a DoD

diff_dod
Read-onlyIdempotent

Compare Definition of Done versions for a task type to identify added, removed, or changed criteria and rules for reviews and retrospectives.

Instructions

What changed in the Definition of Done of a task type between two versions of its file, each merged with its base, or between two versions of the base (type: "base"). Every added, removed or changed criterion and rule names its origin. Defaults: from the previous recorded version to the DoD in force now. For DoD reviews and retrospectives. Read-only.

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": {
      "type": "<type>"
    },
    "name": "diff_dod"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLater version of the file; default: the DoD in force now
fromNoEarlier version of the file; default: the version before `to`
typeYesA task type, or "base" to compare versions of the base

Output Schema

NameRequiredDescriptionDefault
toYes
fromYes
typeYes
rulesYes
summaryYes
criteriaYes
first_seenYes
template_changedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered; the closing "Read-only" adds nothing new. The description does add value beyond annotations by disclosing the default comparison range and that every added, removed or changed criterion and rule is attributed to its origin.

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?

The opening sentence is long but front-loaded with the core question ("What changed...") and each clause carries information: modes, origin attribution, defaults, use case. The trailing "Read-only." is redundant with the annotations and is the only wasted element.

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?

With an output schema present, the description need not explain return values, and it covers the non-obvious parts an agent needs: default range, base-mode versus task-type mode, and origin attribution. It does not address invalid or out-of-range version numbers, a minor gap for a read-only diff.

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% and the schema already documents from/to defaults and the special "base" value of type. The description reinforces the "base" option and the merge-with-base semantics, but adds little on how from/to are resolved beyond what the schema states, so the baseline of 3 applies.

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?

Names a specific operation (diff) and resource (Definition of Done of a task type) and enumerates the two comparison modes: two file versions merged with their base, or two versions of the base selected via type "base". This is clearly distinguishable from get_dod (fetch) and check_dod (validate) 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete use context ("For DoD reviews and retrospectives") and states the default comparison window (previous recorded version to the DoD in force now), which tells the agent it can call the tool with no version arguments. No explicit when-not condition or named alternative is given, so it stops short of a 5.

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