Skip to main content
Glama

Commit a Recipe Research Upload

commit_recipe_research_upload
DestructiveIdempotent

Verify and commit one completed chunk upload as the build's research evidence.

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_research_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.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds one piece of genuine behavior beyond that — the server 'verifies' the chunk before committing — but says nothing about what commit destroys or overwrites, what happens when the sha256 check fails, or whether the commit is final.

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?

The single sentence is front-loaded with the verb and free of filler, which is good. But for a five-required-parameter, destructive, idempotent commit operation it is under-specified rather than concise — the terseness costs information an agent needs.

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. However, for a destructive commit with five undocumented required parameters, the definition omits the prerequisite upload step, the meaning of revision and idempotency_key, and any consequence of a failed verification — significant gaps relative to the tool's 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?

All five parameters are required with 0% schema description coverage, so the description carries the full burden and largely fails it: 'chunk upload' loosely implies chunk_id and 'verify' loosely implies sha256, but revision and idempotency_key receive no meaning at all. No format, provenance, or retry semantics are explained beyond the bare patterns in the schema.

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 gives a specific verb pair ('verify and commit') and a specific resource ('one completed chunk upload'), and the qualifier 'as the build's research evidence' implicitly separates it from the acceptance and spec upload commits among its siblings. An agent can identify the operation without opening the schema, though it never names the sibling it is not.

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 explicit when-to-use guidance, no prerequisite chain (e.g. that a chunk must already be uploaded via begin/append_recipe_build_upload before it can be committed), and no routing to the acceptance or spec commit variants. The word 'completed' hints that a prior step exists but does not state it.

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