Skip to main content
Glama

Set Recipe Acceptance Cases

set_recipe_acceptance_cases
DestructiveIdempotent

Replace the complete behavioral acceptance suite of one private build.

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": {
      "build_ref": "<build_ref>",
      "revision": "<revision>",
      "idempotency_key": "<idempotency_key>",
      "suite": "<suite>"
    },
    "name": "set_recipe_acceptance_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
suiteYes
revisionYes
build_refYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and closed-world scope, so the safety profile is covered structurally. The description corroborates this by saying the entire suite is replaced (implying existing cases are discarded) and limiting scope to a single private build, but it does not explain revision-based concurrency, what happens on a stale revision, or the effect of the idempotency key.

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?

A single tight sentence with the destructive replace action front-loaded. No filler, no redundancy.

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

Completeness2/5

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

This is a complex nested-payload mutation with a rich output schema and four required parameters, yet the description covers none of the operational semantics an agent needs: stale-revision handling, idempotency behavior, limits on the suite contents, or which sibling generates a valid suite. A one-liner is too thin for this level of complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description says nothing about build_ref, revision, idempotency_key, or the suite structure. The schema is rich and largely self-describing in shape, but the semantics of key parameters — notably revision as a concurrency token and idempotency_key's replay behavior — are left undocumented in both places.

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 uses a specific verb-plus-resource ('Replace the complete behavioral acceptance suite') and scopes it to 'one private build', which separates it from adjacent suite-setting siblings such as set_recipe_contracts and set_recipe_metadata. It stops short of naming a sibling or stating how it differs from the quote/commit acceptance tools.

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

Usage Guidelines3/5

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

'Replace the complete ... suite' implies whole-suite overwrite semantics, which hints at when to use it rather than an incremental update, but there is no explicit when-to-use, no preconditions (e.g. validating first via quote_recipe_acceptance or get_recipe_acceptance_plan), and no exclusions.

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