Skip to main content
Glama

Commit a Recipe Acceptance Upload

commit_recipe_acceptance_upload
DestructiveIdempotent

Verify and commit one completed chunk upload as the full acceptance suite.

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>",
      "chunk_id": "<chunk_id>",
      "sha256": "<sha256>"
    },
    "name": "commit_recipe_acceptance_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
sha256Yes
chunk_idYes
revisionYes
build_refYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, so the safety profile is carried by structured data. The description adds one genuinely new behavioral fact — that a verification step precedes the commit — but says nothing about what is destroyed or replaced (an existing acceptance suite?), what a verification failure looks like, or how idempotency_key governs retries.

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?

A single front-loaded sentence with no filler; the verify-then-commit ordering is expressed compactly. It is arguably too terse for a destructive five-parameter mutation, but nothing in it is wasted.

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?

An output schema exists so return values need not be explained, but for a destructive commit with five required, undocumented parameters the description leaves out prerequisites, the meaning of "full acceptance suite", failure behavior, and retry/idempotency semantics. An agent could invoke it but could not predict its effect or recover from an error based on this text alone.

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, so the description must compensate and largely does not. "Chunk upload" loosely maps to chunk_id and "verify" hints at the sha256 integrity check, but build_ref, revision, and idempotency_key are never mentioned and no format, constraint, or retry semantics are explained.

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?

"Verify and commit one completed chunk upload as the full acceptance suite" gives a concrete verb pair (verify, commit) and a concrete resource (a completed chunk upload becoming the acceptance suite). The word "acceptance" implicitly separates it from the research/spec upload commits among the siblings, though an agent must already know the recipe domain vocabulary to be sure.

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?

Usage is only implied: "one completed chunk upload" hints that the chunk must already exist and be complete before calling, which is useful prerequisite context. But there is no explicit when-to-use vs. the sibling commit_recipe_research_upload / commit_recipe_spec_upload tools, and no statement of what happens if the upload is not yet complete or already committed.

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