Skip to main content
Glama

Release readiness gate

submit_release_readiness_gate
Idempotent

A single go/no-go decision for a release: runs the repository hardening and the supply-chain and licence audit over the same artifacts, combines their findings, and returns a pass or block decision with the blocking findings named. At the end of a release cycle, when a single reproducible pass/block decision is needed. Do not choose this when you need exploitability proven by running the code, or a legal opinion. Example requests: Give me a go/no-go decision for this release. | Is this project safe to ship? Check hardening and licences together. | Which findings block my release? | Run the release readiness gate over these artifacts.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_release_readiness_gate"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds genuinely new behavior — that two analyses are combined over the same artifacts and that the output is a reproducible pass/block verdict naming the blockers. It does not mention that this is a priced capability requiring a quote_id before authorization, which is a notable omission for a job-submitting tool.

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?

It is front-loaded: what it does, when to use it, when not to, then examples. The usage sentence partly restates the opening ("a single go/no-go decision" vs "a single reproducible pass/block decision"), and four example requests are generous, but nothing is misleading and the examples aid routing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a composite tool with a nested five-artifact object and a declared output schema, the description covers purpose, trigger, exclusions and sample phrasing, so an agent can select and invoke it. The remaining gap is the authorization/pricing flow implied by quote_id and accepted_price, which the description never mentions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 75% and every artifact sub-field is documented in the nested schema, so the schema does most of the work. The description adds one meaningful framing — that all five artifacts are evaluated as a single consistent set ("over the same artifacts") — but says nothing about quote_id, accepted_price or authorized_by semantics beyond what the schema already states.

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

Purpose5/5

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

The description states a specific verb and resource — it runs the hardening and supply-chain/licence analyses over the same artifacts and returns a single pass/block decision with the blocking findings named. That composite scope distinguishes it clearly from the single-concern siblings (submit_security_hardening_audit, submit_supply_chain_licence_audit) without the agent needing to open any schema.

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

Usage Guidelines4/5

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

It gives an explicit trigger ("At the end of a release cycle, when a single reproducible pass/block decision is needed") and explicit exclusions ("Do not choose this when you need exploitability proven by running the code, or a legal opinion"). The gap is that the alternatives are described by capability rather than named, so the agent must infer that the excluded cases map to the exploit-running and compliance/legal siblings.

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