Skip to main content
Glama

Append a Recipe Build Upload

append_recipe_build_upload
Idempotent

Append one ordered UTF-8 text chunk to an existing private build upload.

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>",
      "seq": "<seq>",
      "text": "<text>"
    },
    "name": "append_recipe_build_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
seqYes
textYes
chunk_idYes
revisionYes
build_refYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare the safety profile (not read-only, idempotent, non-destructive, closed-world). The description adds genuinely new context beyond them: the payload must be UTF-8, it is one ordered chunk, and the upload is private. It does not disclose what happens on out-of-order or duplicate seq values, nor any size/rate limits, so it is helpful but not rich.

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 or redundancy. Its brevity is efficient, though it leaves the rest of the definition under-explained.

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?

For a six-required-parameter mutation with zero schema descriptions, the definition is far too thin: the sequencing contract for seq, the meaning of revision, and the idempotency guarantee are all undocumented. An output schema exists, so return values need not be covered, but the invocation contract is not.

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% with six required parameters, so the description must carry the burden and it does not. It gives no meaning for revision (a 64-hex hash), idempotency_key (replay behavior), build_ref (format), or seq (whether chunks must be contiguous or how gaps are handled), only loosely hinting at text and chunk_id via 'text chunk'.

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 and resource: appends one ordered UTF-8 text chunk to an existing private build upload. That is clearly distinguishable from begin_recipe_build_upload and commit_recipe_build by the 'one chunk' granularity, though the description never names those siblings to sharpen the contrast.

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?

The word 'existing' implies a precondition (an upload must already have been begun), but there is no explicit when-to-use statement, no mention of when to stop appending versus calling commit_recipe_build, and no guidance on ordering or retry conditions. The agent must infer the whole workflow from the sibling list.

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