Skip to main content
Glama

Preflight a Recipe Build

preflight_recipe_build
Idempotent

Verify commit readiness and issue a short-lived commit capability for one exact qualified build revision.

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>"
    },
    "name": "preflight_recipe_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionYes
build_refYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, readOnlyHint=false and openWorldHint=false. The description usefully adds that the issued capability is short-lived and that readiness is verified (so failure is possible), but says nothing about what disqualifies a revision, whether verification has side effects, or how the capability is consumed.

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 dense sentence with the verification action front-loaded and no filler. It is slightly jargon-heavy ('qualified build revision'), but every clause carries information.

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-value explanation is not needed, and annotations cover the safety profile. However, with three undocumented parameters and no stated relationship to the sibling commit/upload tools, an agent still lacks enough to invoke this confidently in the build lifecycle.

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 all three required parameters, so the description must carry the load and it does not: build_ref format, the meaning of the 64-hex 'revision' beyond 'exact', and the role of idempotency_key are all left unexplained. Only a vague hint that the revision must be 'qualified' is added.

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 compound action: verify commit readiness and issue a short-lived commit capability for one exact qualified build revision. 'Preflight' is effectively disambiguated from the actual commit, so an agent can distinguish it from commit_recipe_build, though no sibling is named.

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?

The word 'preflight' plus 'verify commit readiness' implies this precedes a commit, but the description never states the condition that selects it over commit_recipe_build, nor prerequisites such as the revision already being uploaded or qualified. Usage is inferable rather than stated.

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