Skip to main content
Glama

Axveritas-abvs-gateway

axveritas_preflight_check

Pre-flight URL dead-end check ($0.001 USDC or X-API-Key). Prevents wasted LLM compute on Cloudflare/404 blocks.

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_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add genuinely useful context the schema cannot convey: a $0.001 USDC or X-API-Key payment/auth model and the specific failure classes it detects (Cloudflare blocks, 404s). It omits the return shape, whether the call itself can fail or be rate limited, and whether it performs any network fetch with side effects.

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?

Two tight sentences with the outcome benefit front-loaded and no filler. The payment clause in parentheses is dense but placed where it does not obscure the core purpose.

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

Completeness2/5

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

For a one-parameter tool with no annotations and no output schema, an agent still needs to know what the check returns and how to branch on it; the description says only that it 'prevents wasted compute' without stating the result signal. Combined with the undocumented parameter, the definition leaves too much for the agent to infer.

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

Parameters2/5

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

Schema coverage is 0% for the single required parameter, so the description must compensate. Saying 'URL' weakly signals that target_url is a URL, but it gives no format expectations, no note that the parameter is required, and no mention of validation behavior for malformed input.

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 uses a specific verb phrase, 'Pre-flight URL dead-end check', which tells an agent this validates a URL before further work rather than fetching content. The parenthetical names the payment/auth mechanism. It stops short of contrast with the sibling axveritas_scrape_verified, so an agent must infer that the sibling is the one that actually retrieves content.

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?

'Pre-flight' plus 'Prevents wasted LLM compute on Cloudflare/404 blocks' implies the use case: run this before spending compute on a URL. There is no explicit when-not condition, no statement of what to do after the check returns, and no mention of the scrape sibling as the follow-up alternative, so guidance is only implied.

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