Skip to main content
Glama

Check my x402 endpoint

check_my_x402_endpoint
Read-onlyIdempotent

For x402 sellers: shows whether vet402 finds the endpoint in the catalogs it reads, what happened when vet402 paid it, and when vet402 can buy again. Pass any URL on your host. The answer covers the listings on that host as shown on the public seller page, the failure modes vet402 recorded with links to the fix-first page, and the five most recent purchases with their transactions.

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": "check_my_x402_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAny https URL on your host, such as one of your x402 endpoints.

Output Schema

NameRequiredDescriptionDefault
l0Yes
l1Yes
hostYes
as_ofYes
notesYes
listingsYes
listed_inYes
on_recordYes
page_kindYes
truncatedYes
method_urlYes
record_urlYes
l1_purchasesYes
fix_first_urlYes
listing_sourcesYes
l1_failure_modesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed21 schema fields changed
    • removedOutput schema / properties / fix_first_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / fix_first_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / l0 / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "fail": {
      -        "maximum": 9007199254740991,
      -        "minimum": -9007199254740991,
      -        "type": "integer"
      -      },
      -      "last_checked_at": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "not_probed": {
      -        "maximum": 9007199254740991,
      -        "minimum": -9007199254740991,
      -        "type": "integer"
      -      },
      -      "pass": {
      -        "maximum": 9007199254740991,
      -        "minimum": -9007199254740991,
      -        "type": "integer"
      -      },
      -      "unverified": {
      -        "maximum": 9007199254740991,
      -        "minimum": -9007199254740991,
      -        "type": "integer"
      -      }
      -    },
      -    "required": [
      -      "pass",
      -      "fail",
      -      "unverified",
      -      "not_probed",
      -      "last_checked_at"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "fail": {
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      "last_checked_at": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "not_probed": {
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      "pass": {
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      "unverified": {
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "pass",
      +      "fail",
      +      "unverified",
      +      "not_probed",
      +      "last_checked_at"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / l1_purchases / items / properties / explorer_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / l1_purchases / items / properties / explorer_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / l1_purchases / items / properties / network / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / l1_purchases / items / properties / network / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / l1_purchases / items / properties / tx_hash / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / l1_purchases / items / properties / tx_hash / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / listed_in / items / properties / last_seen_at / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / listed_in / items / properties / last_seen_at / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / listings / items / properties / l0_latest / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / listings / items / properties / l0_latest / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / listings / items / properties / latest_result / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / listings / items / properties / latest_result / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / listings / items / properties / network / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / listings / items / properties / network / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / listings / items / properties / next_purchase_earliest_at / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / listings / items / properties / next_purchase_earliest_at / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / record_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / record_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With readOnlyHint, idempotentHint, and destructiveHint already declared, the description goes beyond them by disclosing the shape of the answer: listings on the host, recorded failure modes with links to a fix-first page, and the five most recent purchases with transactions. That 'five most recent' bound is a real behavioral detail an agent would otherwise not know. It does not mention latency, caching, or what happens if the host is unknown, so it is not exhaustive.

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?

Three sentences, front-loaded with the audience and the three things returned, with no filler. The third sentence is the longest and slightly dense (listing, failures-with-links, purchases in one breath), but each clause carries distinct information.

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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes them usefully and adds the audience and host-scoping constraints a caller needs. For a one-parameter read tool with full annotations this is close to complete; only the absent sibling routing keeps it from a 5.

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

Parameters4/5

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

Schema coverage is 100% and the single parameter is already documented, so the baseline is 3. The description earns one above baseline by clarifying that any URL on the host is acceptable and that the response is host-scoped rather than URL-scoped — an agent could otherwise assume per-endpoint granularity and over-call.

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 — it reports catalog presence, payment outcome, and next-buy eligibility for an x402 endpoint — and names the audience ('For x402 sellers'). The 'answer covers the listings on that host' clause implicitly separates it from a per-endpoint or discovery tool, but it never names check_x402_seller or find_x402_sellers, so the sibling boundary must be inferred.

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?

The audience qualifier ('For x402 sellers') and 'Pass any URL on your host' give implied usage context, but there is no explicit when-to-use/when-not-to-use statement and no routing to check_x402_seller or find_x402_sellers. An agent knows roughly who this is for but not why it would pick this over the two sibling 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.