Skip to main content
Glama

UAI x402 Security Tools

wrangler-config-audit

DevOps security audit for Cloudflare wrangler.toml — flags production-unsafe settings, plaintext secrets in vars, risky routes, and missing observability for Worker deployments. (REST equivalent: POST /api/v1/wrangler-config-audit, $0.05)

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": {
      "wranglerToml": "<wranglerToml>"
    },
    "name": "wrangler-config-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
wranglerTomlYeswrangler.toml contents

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations carry only a title, so no readOnlyHint or destructiveHint is declared; the description implies a non-mutating analysis by calling it an 'audit' that 'flags' issues, but never states this outright. It does add genuinely useful context by disclosing cost ($0.05) and the REST equivalent endpoint, but says nothing about severity scoring, result storage, or rate limits.

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?

A single front-loaded sentence with the checklist of findings before the parenthetical pricing/REST note. No wasted clauses, though the enumerated list could be trimmed without loss.

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 a one-parameter analysis tool the scope is well covered, but with no output schema the description should say what the audit returns (findings list, severity levels, pass/fail verdict) so an agent knows how to interpret and present results. That gap keeps it at minimum-viable completeness.

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 parameter, wranglerToml, with 100% schema description coverage, so the schema already fully documents it. The description adds no format detail beyond what the schema states (e.g., whether the file must be complete or whether includes/vars resolution is expected), 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 states a specific verb and resource ('security audit for Cloudflare wrangler.toml') and enumerates the exact classes of findings: production-unsafe settings, plaintext secrets in vars, risky routes, and missing observability. This clearly separates it from generic sibling scans like terraform-iam-risk-scan, though it never explicitly contrasts itself with cloudflare-worker-security-review.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no named alternative. Only a weak implication of a pre-deployment check from the phrase 'DevOps security audit'; the agent must infer the workflow context.

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