Skip to main content
Glama

cf_validate_wirefilter

Validate Cloudflare Wirefilter expressions with a syntactic check for balanced parentheses, unknown operators, and typos. Reports validity and errors.

Instructions

Best-effort syntactic check of a Cloudflare Wirefilter (Rules language) expression.

NOT a full grammar — catches balanced-paren violations, unknown operator
spellings, and obvious typos. A `{valid: true}` response does NOT
guarantee Cloudflare's evaluator will accept the expression at runtime.

Args:
    expression: the wirefilter source, e.g. `(http.request.uri.path
        contains "/admin" and ip.src in {1.2.3.4 5.6.7.8})`.

Returns: envelope with `data = {valid: bool, errors: list, expression}`.
Note: this tool returns success-envelope even when `valid=false`;
the validator's purpose IS to report syntactic issues.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
expressionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: it is 'best-effort', catches specific issues (balanced-paren violations, unknown operators), and notes that a valid result does not guarantee Cloudflare acceptance. It also explains the envelope format even when validation fails.

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?

The description is concise and well-structured: a main sentence, a caveat, then structured Args/Returns sections. Every sentence adds value, and the information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has one parameter and an output schema is referenced, the description covers the behavior, parameter meaning, result format, and limitations. It is complete for a validation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, but the description explains the 'expression' parameter with an example: 'e.g. `(http.request.uri.path contains "/admin" and ip.src in {1.2.3.4 5.6.7.8})`'. This adds meaning beyond the schema's type string.

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?

The description clearly states the tool's purpose: 'Best-effort syntactic check of a Cloudflare Wirefilter (Rules language) expression.' It specifies the resource (Wirefilter expression) and the action (validate), distinguishing it from sibling tools which are for other Cloudflare operations.

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 description notes it is 'NOT a full grammar' and that a valid response does not guarantee runtime acceptance, implying the tool is for preliminary checks. It does not explicitly state when not to use or provide alternatives, but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wojtekkura/cf-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server