Skip to main content
Glama

aw1-circuit-breaker-remote

aw1_static_ast_preflight

Read-onlyIdempotent

Deterministic dry-run AST and Gate 7 safety preflight scoring for proposed Python or shell payloads without executing or mutating state. Supports x402 per-call payment ($0.002/call in Base USDC).

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": {
      "payload": "<payload>"
    },
    "name": "aw1_static_ast_preflight"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYesProposed Python code or shell command to inspect
languageNoPayload language (python or shell)python

Output Schema

NameRequiredDescriptionDefault
safeYesTrue if payload passes Gate 7 static AST checks
findingsNoDetected AST or shell hazards
risk_scoreYesNormalized risk score from 0 (clean) to 100 (critical)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description does not need to restate safety. It adds genuine context beyond them: determinism, the no-execution/no-mutation guarantee, and a per-call cost of $0.002 via x402 in Base USDC, which is a real constraint an agent must know before invoking.

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?

Two sentences, zero waste, with the core capability and its non-execution guarantee front-loaded. The payment sentence is short and carries actionable cost information rather than filler.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. What remains thin is the meaning of 'Gate 7' and the scoring semantics (scale, pass threshold) and failure behavior for unsupported payloads, which the agent would still have to discover at call time.

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 100%, so both parameters are already documented in structured form. The description reinforces that payload means Python code or a shell command and names 'python or shell' as the language values, but adds no syntax, size, or validation detail beyond the schema.

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: deterministic dry-run AST and Gate 7 safety preflight scoring for proposed Python or shell payloads. The phrase 'without executing or mutating state' implicitly distinguishes it from the sibling aw1_execute_protected_tool, though no sibling is named and 'Gate 7' is left undefined as internal jargon.

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 is implied: inspect a payload before running it. There is no explicit when-to-use statement, no exclusion criteria, and no routing guidance toward aw1_execute_protected_tool or aw1_audit_dossier_lookup after a preflight result.

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