Skip to main content
Glama

Begin a Recipe Build Upload

begin_recipe_build_upload
Idempotent

Begin one bounded chunked upload for a private recipe 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>",
      "chunk_id": "<chunk_id>"
    },
    "name": "begin_recipe_build_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
chunk_idYes
revisionYes
build_refYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only the notion of a single bounded chunk, and never explains what "bounded" means (size limits), what state a failed or repeated call leaves behind, or how the upload is finalized. For a mutating upload primitive with no annotation coverage of size/state semantics, this is thin.

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?

One short sentence with no filler and the core action front-loaded. It is efficient, but the brevity is achieved by omitting needed information rather than by precise phrasing, so it falls short of a 5.

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 described, but a mutating first-step tool in a chunked-upload family still needs sequencing, size/chunking rules and parameter meaning. None of that is present, leaving the agent unable to determine how this call fits between preflight/start_recipe_build and append/commit_recipe_build_upload.

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 all four parameters (build_ref, revision, idempotency_key, chunk_id) are required with no textual explanation, so the description carries the full burden and largely fails to meet it. "Chunked upload" hints that chunk_id selects a chunk, but build_ref, the 64-hex revision, and the idempotency_key contract are entirely unexplained. The 64-character hex pattern strongly suggests a content hash for the chunk, yet the description never confirms this.

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 ("Begin") and a resource ("one bounded chunked upload for a private recipe build"), so the general intent is recoverable. However, it never distinguishes this from the closely named siblings append_recipe_build_upload and commit_recipe_build_upload, and "bounded chunked upload" is unexplained jargon. An agent knows roughly what domain it is in but not what this specific call accomplishes versus its neighbours.

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

Usage Guidelines1/5

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

There is no when-to-use guidance at all: no statement that this is the first step of a multi-call upload sequence, no indication of when to call append_recipe_build_upload next, and no prerequisites or exclusions. The word "Begin" weakly implies sequencing, but nothing tells the agent which alternatives exist in this family or when one is chosen over another.

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