Skip to main content
Glama

Set Recipe Build Contracts

set_recipe_contracts
DestructiveIdempotent

Replace the declared input and output contracts 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>",
      "input_contract": "<input_contract>",
      "output_contract": "<output_contract>"
    },
    "name": "set_recipe_contracts"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionYes
build_refYes
input_contractYes
idempotency_keyYes
output_contractYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered externally. The word 'Replace' adds real value by signalling wholesale substitution rather than merge, but the description says nothing about stale-revision rejection, what happens to prior contracts, or how idempotency_key is scoped.

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 front-loaded sentence with no filler; the scoping detail ('one private build') is placed where it is read first. Nothing is redundant.

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 destructive, nested five-parameter mutation, and an output schema exists so return values need no explanation, but the preconditions and parameter meanings that an agent must know before calling are simply absent. One sentence is too thin for this 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% across five required parameters, and the description only implicitly maps to input_contract and output_contract. It never explains build_ref, the 64-hex revision (clearly an optimistic-concurrency token), or idempotency_key, nor the semantic difference between input fields' boolean 'required' and output fields' const-true 'required'.

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?

States a specific verb ('Replace') and a specific resource ('declared input and output contracts of one private build'), including the scope limitation to a single private build. The replace-vs-read distinction from get_recipe_build_contracts is implicit in the verb, but no sibling is named and the boundary with set_recipe_metadata or set_recipe_acceptance_cases is left to inference.

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 guidance on when to call this instead of the getter or the other set_* tools, and no stated prerequisites such as which build states accept contract changes or whether the supplied revision must match the current one. The agent must infer everything about call conditions.

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