Skip to main content
Glama

x402index__verdict

Vet x402 sellers before you pay: live 402 charge decode, fairness vs a 59k-listing index, and a one-call full-catalog audit. New: /pick finds the right paid endpoint for a task. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/x402index/verdict

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402index__verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / base
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / limit
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / task
      Added value: +{
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / base
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / resource
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed3 schema fields changed
    • removedInput schema / properties / budget_usd
      Removed value: -{
      -  "type": "number"
      -}
    • addedInput schema / properties / resource
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / url
      Removed value: -{
      -  "type": "string"
      -}
  4. Changed3 schema fields changed
    • addedInput schema / properties / budget_usd
      Added value: +{
      +  "type": "number"
      +}
    • removedInput schema / properties / resource
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / url
      Added value: +{
      +  "type": "string"
      +}
  5. Changed3 schema fields changed
    • removedInput schema / properties / days
      Removed value: -{
      -  "type": "number"
      -}
    • addedInput schema / properties / resource
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / resources
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
  6. Changed4 schema fields changed
    • addedInput schema / properties / days
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / resources
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • removedInput schema / properties / urls
      Removed value: -{
      -  "description": "Comma-separated https x402 endpoints to vet (up to 20). POST body may instead be {\"urls\": [...]}",
      -  "type": "string"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "urls"
      -]
  7. Changed3 schema fields changed
    • removedInput schema / properties / resource
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / urls
      Added value: +{
      +  "description": "Comma-separated https x402 endpoints to vet (up to 20). POST body may instead be {\"urls\": [...]}",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "urls"
      +]
  8. Changed4 schema fields changed
    • removedInput schema / properties / resource / description
      Removed value: -"The x402 endpoint URL to check. Alias: url."
    • removedInput schema / properties / resources
      Removed value: -{
      -  "description": "Batch mode: up to 25 URLs in one call",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedInput schema / properties / url
      Removed value: -{
      -  "description": "Alias for resource",
      -  "type": "string"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "resource"
      -]
  9. Changed2 schema fields changed
    • changedInput schema / properties / resource / description
      Previous value: -"The x402 endpoint URL to investigate"New value: +"The x402 endpoint URL to check. Alias: url."
    • changedInput schema / properties / resources / description
      Previous value: -"Batch: up to 25 endpoint URLs in one call"New value: +"Batch mode: up to 25 URLs in one call"
  10. Changed1 schema field changed
    • addedInput schema / properties / resources
      Added value: +{
      +  "description": "Batch: up to 25 endpoint URLs in one call",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  11. Changed3 schema fields changed
    • addedInput schema / properties / resource / description
      Added value: +"The x402 endpoint URL to investigate"
    • addedInput schema / properties / url
      Added value: +{
      +  "description": "Alias for resource",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "resource"
      +]
  12. Changed4 schema fields changed
    • removedInput schema / description
      Removed value: -"Send exactly one of: resource/url (single) or resources (batch, max 25)."
    • removedInput schema / properties / resource / description
      Removed value: -"One x402 endpoint URL to vet (single mode)"
    • removedInput schema / properties / resources
      Removed value: -{
      -  "description": "Batch mode: up to 25 endpoint URLs to vet in one call, worst score first",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedInput schema / properties / url
      Removed value: -{
      -  "description": "Alias for resource",
      -  "type": "string"
      -}
  13. First observed

TDQS

B3.1/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 disclose the critical behavior: the call costs $0.01 USDC on Base (eip155:8453) and payment is supplied via params._meta["x402/payment"], plus the concrete HTTP GET endpoint. It omits whether the operation is read-only, rate limits, and what a response contains, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded and the payment/endpoint details earn their place, but the sentence promoting '/pick' reads as marketing for another tool and adds ambiguity. The description is also dense and run-on, folding cost, protocol, and transport into one block.

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 paid, no-annotation tool with no output schema, the description covers cost and payment mechanics well, which is the hardest part to infer. However, it leaves the two input parameters undefined and gives no sense of what the verdict result looks like, so it is only partially complete.

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 two parameters ('task', 'limit'), so the description must compensate and largely does not. The word 'task' appears only in the sentence about the separate /pick feature, and 'limit' is never mentioned, so an agent gets no meaning for either parameter from the description.

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 ('Vet x402 sellers before you pay') and enumerates concrete capabilities: live 402 charge decode, fairness vs a 59k-listing index, and full-catalog audit. It is muddied by an aside advertising '/pick finds the right paid endpoint for a task', which is a different capability and even exists as the sibling x402index__pick, so an agent could mistake this tool for a router.

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?

The phrase 'before you pay' gives a situational cue, but there is no explicit when-not or alternative guidance despite many overlapping siblings (x402check__check, x402_preflight__verify, pageaudit__vet, x402index__pick). Advertising '/pick' inside this description blurs the routing decision rather than clarifying it.

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