Skip to main content
Glama

CraftCI - Automated UX Craft & Billing-Safety CI Gate

craft_verify_billing_safety

Read-onlyIdempotent

Audit TypeScript/JavaScript payment and webhook handlers against the 5 critical Financial & Webhook Security rules (401/403, server SKU pricing, HMAC, idempotency, zero PII logs).

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": {
      "code": "<code>"
    },
    "name": "craft_verify_billing_safety"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesPayment or webhook handler source code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real context beyond that by enumerating the five concrete security rules being checked, which tells the agent what classes of findings to expect. It does not describe the verdict/report format, so not a 5.

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?

One front-loaded sentence that carries the verb, the target, and the rule list with no filler. Every clause adds information an agent would otherwise have to guess.

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 simple single-input analysis tool with full schema coverage and annotations covering safety, the definition is nearly self-sufficient. The one remaining gap is that no output schema exists and the description says nothing about the shape of the audit result (pass/fail vs. per-rule findings).

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% for the single 'code' parameter, which the schema already labels as payment or webhook handler source code. The description only adds the language restriction (TypeScript/JavaScript), so it sits at the high-coverage baseline of 3.

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?

Uses a specific verb ('Audit') on a specific resource ('TypeScript/JavaScript payment and webhook handlers') and names the exact rule set applied (401/403, server SKU pricing, HMAC, idempotency, zero PII logs). That scope clearly separates it from a generic snippet auditor such as craft_audit_code_snippet.

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?

The target scope (payment and webhook handlers in TS/JS) is an explicit usage trigger, so an agent knows when this tool applies rather than the generic audit sibling. It stops short of naming an alternative or stating when not to use it, so it is short of a 5.

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.