Skip to main content
Glama

run_release_preflight_audit

Audit repository and package artifacts before release to verify version alignment, Polar.sh link integrity, canonical $10/mo pricing, and visualizer math concordances.

Instructions

Audits repository and package artifacts for version alignment, Polar.sh link integrity, canonical pricing ($10/mo), and interactive visualizer math concordances before deployment or release.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "run_release_preflight_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_dirNoBase directory of the repository (default: current working directory)..

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. 'Audits' strongly implies a read-only inspection, which is helpful, but the description never states whether the tool mutates files, whether it fails or returns a report on mismatch, or whether checking 'Polar.sh link integrity' requires outbound network access — a significant operational trait left undisclosed.

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 a single dense sentence with the verb and resource front-loaded and no filler. The enumerated check list makes it long but every clause names a distinct check, so the length is largely earned, though the parenthetical '($10/mo)' is oddly specific detail for a description.

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?

With no annotations and no output schema, the description must convey both safety and result shape. It covers scope and checks adequately, but an agent still cannot tell what the audit returns, whether failure is signalled by error or by report content, or what prerequisites (network, repo layout) it assumes.

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?

There is a single optional parameter (base_dir) and schema coverage is 100%, so the schema already fully documents its meaning and default. The description adds nothing about how base_dir scopes the audit (e.g., whether artifacts outside that directory are skipped), so the baseline of 3 applies.

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 description uses a specific verb ('Audits') with a clear resource ('repository and package artifacts') and enumerates the four concrete checks it performs (version alignment, Polar.sh link integrity, canonical pricing, visualizer math). This is far more specific than a restated name, though the enumerated checks are opaque domain jargon that an agent cannot fully interpret without outside knowledge.

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 phrase 'before deployment or release' supplies a clear timing trigger, which is genuine usage guidance. However, there is no guidance on when NOT to use it, no mention of what to do if the audit reports mismatches, and no reference to any alternative or follow-up tool.

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