Skip to main content
Glama

axveritas_scrape_verified

Direct verified web extraction ($0.015 USDC on Base). Fetches target_url, strips junk HTML, asserts required JSON keys, and returns clean data with an ABVS-1.0 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>",
      "required_keys": "<required_keys>"
    },
    "name": "axveritas_scrape_verified"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_urlYesWebpage URL to extract
required_keysYesMandatory JSON keys

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 a genuine behavioral fact: a $0.015 USDC cost on Base, i.e. a paid call. It also describes the internal pipeline and that an ABVS-1.0 receipt is returned. However, it never says what happens when required_keys are missing (error, partial result, refund), nor any rate limits or receipt contents.

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 dense sentences, front-loaded with cost and capability, with no filler. The trailing "ABVS-1.0" token is slightly opaque but plausibly useful as a receipt identifier.

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 two-parameter tool with full schema coverage and no output schema, the description covers cost, processing steps, and that a receipt accompanies results, which is reasonable. It stops short of the failure/error contract, which matters for a paid, assertion-based tool where a failed assertion could still incur cost.

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 100%, so the baseline is 3, but the description only restates the parameters ("fetches target_url", "asserts required JSON keys") without adding format, behavior-on-failure, or example semantics. The one implicit addition is that a key mismatch is asserted against, but the consequence is unstated.

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?

"Direct verified web extraction" gives a specific verb and resource, and the following sentence enumerates the pipeline (fetch, strip, assert, return). The word "Direct" hints at the distinction from axveritas_verify_scrape, but the sibling is never named or contrasted explicitly.

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 statement of when to choose this tool over axveritas_verify_scrape, nor any prerequisite or exclusion. An agent must infer from "Direct" that this is the one-shot, non-verifying path, which is weak guidance for a pair of similarly named tools.

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