Skip to main content
Glama
GodPrompt MCP Server

GodPrompt MCP Server

Assess reported release readiness

assess_release_readiness
Read-onlyIdempotent

Checks caller-reported CI status, source and artifact revisions, rollback and migration plans, and approvals to find missing release blockers; does not authorize deployment or authenticate receipts.

Instructions

Check caller-reported CI checks, source/artifact revision, rollback, migration and approvals for missing blockers; never authorize deployment or authenticate receipts.

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": {
      "target": "<target>",
      "checks": "<checks>"
    },
    "name": "assess_release_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
checksYes
targetYes
rollback_planNo
migration_planNo
source_revisionNo
approval_reportedNo
artifact_revisionNo
migration_involvedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.2

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description still contributes real behavioral context: it only reasons over caller-reported inputs (no external verification) and explicitly disclaims authorization/attestation powers, which prevents an agent from treating a passing result as a deploy gate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the operative clause ('for missing blockers') placed before the disclaimers, so the core purpose lands first. No redundant restatement of the title or the tool name.

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?

For an 8-parameter read-only evaluator with no output schema and zero schema descriptions, the definition should say what the result looks like (e.g., a list of detected blockers) and how the plan/revision fields are interpreted. As written, an agent knows what inputs are examined but not what comes back, which is a meaningful gap given the missing output schema.

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 0%, so the description must carry the burden, and it does map six of the eight parameters (checks, source_revision, artifact_revision, rollback_plan, migration_plan, approval_reported) to their apparent role. It omits 'target' and 'migration_involved' and never explains what counts as a 'missing blocker' or how the plan fields are judged, leaving key semantics underspecified.

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 definition gives a specific verb ('Check') and an enumerated set of resources (CI checks, source/artifact revision, rollback, migration, approvals) plus the goal ('for missing blockers'). The qualifier 'caller-reported' usefully scopes it as an evaluator of supplied evidence rather than a fetcher, which differentiates it in spirit from verification-style siblings, though no sibling is named outright.

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?

Usage context is implied by 'reported' and 'for missing blockers', and the negative clause 'never authorize deployment or authenticate receipts' sets a boundary on what the caller should expect. However, there is no explicit when-to-use versus alternatives (e.g., get_gates or review_work_evidence) and no stated prerequisites for calling it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.