Skip to main content
Glama

apex-dev

Delivery score

delivery_score

Free sample: https://apexfaucet.xyz/delivery-score?url=https://apexfaucet.xyz/api/x402/page-markdown ($0.003). Score one https x402 URL from 0 to 100. Five parts of 0 to 20: watchtower 7-day uptime for that exact URL, a valid unpaid 402, the USDC price, how fast that probe was, and test buys we already recorded. This call does not pay the URL. A URL we have never bought scores 0 on test buys and says so. $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "url": "<url>"
    },
    "name": "delivery_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps x402 URL to score. This call does not pay it.
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the call is non-paying, that an unbought URL scores 0 on the test-buys component, the exact price ($0.003/call), and the accepted rails (USDC on Arc, Base or Solana, or XNT on X1). It does not describe the response shape or failure modes for an invalid or unreachable URL, which is the remaining behavioral gap.

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?

It is dense and front-loads the core purpose before the pricing and payment mechanics, with no filler sentences. The leading 'Free sample' URL is somewhat promotional and competes with the actual explanation for attention, but it does serve as a discoverable example.

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

Completeness4/5

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

For a two-parameter paid tool with no annotations and no output schema, the description covers purpose, score composition, cost, payment rails, and the two-call protocol — enough for an agent to invoke it correctly. The absence of output-schema detail means the exact response payload remains unstated.

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 description coverage is 100%, and the description largely restates the schema — 'https x402 URL to score. This call does not pay it' and the signed-payment explanation appear in both places. It adds only the sequencing context that passing `payment` completes the purchase inside the call, which is useful but marginal, so baseline 3 applies.

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 gives a specific verb and resource — 'Score one https x402 URL from 0 to 100' — plus the five 0-20 components that make up the score, so the agent knows exactly what the call returns conceptually. It never distinguishes itself from the sibling delivery_receipt, leaving the boundary between the two unclear.

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 invocation path is explicit: call once without `payment` for terms, sign with your own wallet, call again with `payment`. It also states the negative case clearly ('This call does not pay the URL'). It does not say when to choose this over alternatives such as delivery_receipt, so it stops short of full routing guidance.

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