Skip to main content
Glama

Commit a Recipe Specification Upload

commit_recipe_spec_upload
DestructiveIdempotent

Verify and commit one completed chunk upload as the full recipe specification.

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_spec_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

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=true, and openWorld=false, so the safety profile is largely covered. The description adds only the word 'verify', hinting at a validation gate before commit, but says nothing about what destructive replacement means here (does it overwrite an existing recipe spec?), what happens when verification fails, or how idempotency_key interacts with retries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no filler, so nothing is wasted, but the terseness comes at the cost of under-specification rather than efficiency. The most critical information (verification criteria, destructive replacement, ordering) is absent rather than front-loaded.

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?

An output schema exists, so return values need not be explained, and the annotations convey the mutation/idempotency profile. Still, for a destructive commit operation with five undocumented required parameters, the description leaves out the verification contract, failure behavior, and the upload lifecycle context that an agent needs to invoke it correctly.

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?

All five parameters are required with 0% schema description coverage, so the description carries the full burden and largely fails. 'Verify' loosely gestures at sha256 and 'chunk upload' at chunk_id, but build_ref, revision, and idempotency_key are given no meaning at all — no format hints, no note that sha256 must match the chunk, no retry semantics for idempotency_key.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb+resource pair ('verify and commit one completed chunk upload') and names the object as the 'full recipe specification', so the rough action is identifiable. However, 'one completed chunk upload as the full recipe specification' is genuinely ambiguous: it is unclear whether the chunk becomes the whole spec or is merely the last piece being finalized, and it never differentiates itself from the similarly named commit_recipe_acceptance_upload / commit_recipe_research_upload siblings.

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 when-to-use guidance, no mention of the required prior step (begin/append upload) that would make a chunk 'completed', and no named alternative for the acceptance or research upload variants. The agent must infer sequencing entirely from the name and required parameters.

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