Skip to main content
Glama

Axveritas-abvs-gateway

axveritas_scrape_verified

Direct schema-verified web extraction ($0.015 USDC or X-API-Key) with ABVS-1.0 SHA-256 receipt.

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_scrape_verified"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_urlYes
required_keysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With zero annotations the description carries the full burden, and it does disclose genuinely useful behavior: a per-call cost of $0.015 USDC, an alternative X-API-Key auth path, and that a SHA-256 receipt is produced. It omits what happens on verification failure, whether extraction renders JavaScript, rate limits, and what the receipt or payload looks like.

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 no filler; cost and auth are packed into a parenthetical. The only waste is the unexplained 'ABVS-1.0' token, which occupies space without conveying actionable meaning.

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 2-parameter tool with no annotations and no output schema, the description leaves too much unsaid: the meaning of required_keys, the shape of the returned extraction, the failure mode when verification fails, and any relationship to preflight_check. Pricing and auth are covered, but the operational picture is not.

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 description coverage is 0% and the description never mentions either parameter. 'required_keys' is completely opaque — an agent cannot infer that it is a list of keys that must be present in the extracted output — and target_url gets no format or constraint detail. 'schema-verified' gestures at the concept but does not explain the parameter.

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 recognizable verb+resource pair (web extraction) and adds differentiating modifiers: schema-verified, and an ABVS-1.0 SHA-256 receipt. It does not name or contrast with the sibling axveritas_preflight_check, and 'ABVS-1.0' is unexplained jargon an agent cannot act on, so it falls short of a 5.

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 when-to-use or when-not guidance, and no mention of the sibling preflight_check that an agent would plausibly need to call first. The only routing signal is the price/auth parenthetical, which tells the agent how it will be charged, not when this tool is the right choice.

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