Skip to main content
Glama

Write acceptance criteria for an AI feature

write_acceptance_criteria
Read-onlyIdempotent

Acceptance criteria for an AI feature or user story that can actually be tested: Given/When/Then with measurable pass bars on a test set, must-pass safety criteria, latency and cost budgets, and example test cases, ready to paste into a ticket. Returns instructions to follow with the user's text.

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

Input Schema

NameRequiredDescriptionDefault
featureNoThe AI feature or user story, who uses it, and what it must never do

Output Schema

NameRequiredDescriptionDefault
textYesThe answer in markdown, as shown to the user; for the guides, instructions to follow with the user's text
linksYesThe AI PM Lab pages the answer links to, where each idea can be tried hands-on

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "links": {
      +      "description": "The AI PM Lab pages the answer links to, where each idea can be tried hands-on",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "text": {
      +      "description": "The answer in markdown, as shown to the user; for the guides, instructions to follow with the user's text",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "text",
      +    "links"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered structurally. The description contributes one genuinely useful behavioral fact — 'Returns instructions to follow with the user's text,' i.e. it emits guidance rather than a finished artifact — but that sentence is cryptic and doesn't say what the instructions look like or how the caller should apply them.

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?

One compact sentence front-loads the deliverable and enumerates its components without padding. It is a sentence fragment with no verb, and the trailing 'Returns instructions...' clause is tacked on rather than integrated, which costs a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The enumerated criteria (pass bars, safety must-pass, latency/cost budgets, example cases) make the deliverable adequately clear, and an output schema exists so return values needn't be spelled out. What is missing is the decision context: with 17 siblings including an evaluator-design tool and a spec reviewer, the description never says which situations call for this one.

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?

Only one parameter and the schema already carries a 100% coverage description ('the AI feature or user story, who uses it, and what it must never do'). The description's list of criteria types describes the output, not the input, so it adds little to what the schema states; baseline 3 applies when schema coverage is complete.

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?

Names a specific artifact (acceptance criteria with Given/When/Then, safety, latency and cost budgets, example test cases) for a specific subject (an AI feature or user story), which is far more concrete than the title alone. It does not, however, distinguish itself from nearby siblings like design_eval_suite or review_ai_spec, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to reach for this tool versus alternatives such as design_eval_suite (which also produces testable criteria) or review_ai_spec. 'Ready to paste into a ticket' hints at a pre-implementation authoring use case but is never made explicit, and no prerequisites or exclusions are given.

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.

Resources