Skip to main content
Glama

axveritas_preflight_check

Fast $0.001 USDC Dead-End Sign check before scraping or burning LLM tokens. Checks shared network telemetry + fast probe to warn if a URL is blocked by Cloudflare, 404, or rate-limited.

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": {
      "target_url": "<target_url>"
    },
    "name": "axveritas_preflight_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_urlYesURL to check for dead-end blocks before scraping

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful traits: a $0.001 USDC cost, and that the verdict draws on shared network telemetry plus a fast probe. However, it never says what the result actually looks like (a boolean, a status enum, a warning string) despite having no output schema, nor does it explain the USDC payment/auth requirement implied by the price.

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 tight sentences that lead with cost and purpose, then the detection scope. Every clause adds information; nothing is redundant with the title or schema.

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 read-only probe this is close, but the tool's entire value is its verdict, and the description does not indicate the shape of that verdict or how an agent should branch on it. The paid-telemetry aspect (USDC charge, shared cache staleness) also goes unexplained relative to the tool's simplicity.

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 coverage is 100% for the single target_url parameter, so the schema already documents it; the description only restates it as the URL checked for dead-end blocks. Baseline 3 applies since there is no additional syntax, normalization, or format guidance 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: a pre-scrape check of a URL for 'dead-end' blocks, and enumerates what it detects (Cloudflare block, 404, rate-limit). The 'before scraping' framing distinguishes it from the sibling scrape tools, though it never names them.

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?

Gives clear context for when to call it ('before scraping or burning LLM tokens'), which is the correct decision point. It stops short of explicit when-not guidance or naming axveritas_scrape_verified as the tool to use after a passing preflight.

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