Skip to main content
Glama

Stride — AI software delivery platform

by page.stride
OverviewDiscussionsAdmin

Create test cases from acceptance criteria

stride.create_test_case_from_ac

Create test cases from a story's acceptance criteria, each linked back to its criterion (relation covers_ac). Required: storyId (ticket key like "OP-12" or UUID) plus exactly one of: acId (ONE criterion), acIds (several, up to 50), or allCriteria: true (every criterion of the story, one call instead of one per criterion). The ac_… ids come back from stride.create_story and stride.get_story (acceptanceCriteria[].id) — no separate get_story_context read is needed. Idempotent per criterion: an already-covered criterion returns its existing case (alreadyExisted) and writes nothing; the multi mode returns a per-criterion receipt (created / alreadyExisted) plus notFound ids. Optional: templateId (a test-case template; its title pattern may use {{acText}} and {{storyTitle}}, and its steps/type/priority/expectedResult are applied), suiteId (defaults to the project's first suite). Without a template the title is "Verify: ", type INTEGRATION, priority MEDIUM, status DRAFT. Use stride.create_test_case when a case should cover a whole story instead.

Input Schema

NameRequiredDescriptionDefault
acIdNoONE acceptance-criterion id (ac_…) from stride.get_story / create_story / get_story_context. Exactly one of acId, acIds, allCriteria.
acIdsNoSeveral criterion ids in one call; per-criterion receipt. Exactly one of acId, acIds, allCriteria.
storyIdYesStory UUID or ticket key (e.g. "OP-12").
suiteIdNoTest suite UUID in the same project; defaults to the first suite.
templateIdNoTest-case template UUID (workspace-shared or same project).
allCriteriaNotrue = every acceptance criterion of the story in one call. Exactly one of acId, acIds, allCriteria.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior1/5

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

The description claims 'Idempotent per criterion' and says an already-covered criterion writes nothing, but the annotations declare idempotentHint=false. This is a direct contradiction; despite otherwise useful behavioral details about defaults and receipts, the contradiction forces a 1 under the rules.

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 purpose is front-loaded and the remaining sentences are dense with operational details: required identifiers, mode exclusivity, idempotency behavior, template/default behavior, and sibling routing. There is little filler for a complex tool.

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?

For a six-parameter creation tool with no output schema, the description is unusually complete. It explains how to obtain ac_ ids, what each mode returns, template and suite defaults, creation defaults, and when to use the sibling tool instead.

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 already 100%, but the description adds meaningful semantics beyond the schema: acIds is capped at 50, allCriteria creates every criterion in one call, templateId supports title patterns with {{acText}} and {{storyTitle}}, and suiteId defaults to the project's first suite.

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 description uses a precise verb and resource: create test cases from a story's acceptance criteria, linked via covers_ac. It explicitly distinguishes itself from stride.create_test_case by saying to use that sibling when a case should cover a whole story instead.

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

Usage Guidelines5/5

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

It states the required storyId and the mutually exclusive selection modes: exactly one of acId, acIds, or allCriteria. It also names the alternative sibling and the condition for choosing it, so an agent can route correctly without inference.

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

All Stride — AI software delivery platform toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources