Skip to main content
Glama

Agoranome buyer checks and market data

Listing lint

lint_listing
Read-only

Why isn't my x402 API in the Bazaar? Listing lint checks an x402 endpoint for Bazaar indexing: one unpaid call validates its 402 PAYMENT-REQUIRED header, discovery metadata, input and output schemas, description limits and service name against the indexing rules, with a fix for each problem and the fixed 402 ready to paste, graded as the weekly report card would grade it. Also lints A2A agent cards. Use when an agent needs to lint an x402 listing or A2A agent card before its first sale. Free: no payment is asked.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic https URL of the paid endpoint, or of an A2A agent card (/.well-known/agent-card.json)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / kyapay-token
      Removed value: -{
      -  "description": "A Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.",
      -  "type": "string"
      -}
  2. Changed1 schema field changed
    • addedInput schema / properties / kyapay-token
      Added value: +{
      +  "description": "A Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Public https URL of the paid endpoint"New value: +"Public https URL of the paid endpoint, or of an A2A agent card (/.well-known/agent-card.json)"
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds real context beyond them: it performs exactly one unpaid call, no payment is asked, it returns a fix per problem, a corrected 402 ready to paste, and a grade matching the weekly report card. That discloses cost, side effects and return shape for a read-only network call.

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?

Front-loaded with the user-facing question and then a dense enumeration of what is checked. The middle sentence is long and clause-heavy, but every clause carries information (checks, fixes, grade, free call); there is little true waste.

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

Completeness5/5

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

For a one-parameter, read-only tool with no output schema, the description covers what it inspects, what it returns (per-problem fixes, a paste-ready fixed 402, a grade), that it is free, and the A2A variant. Nothing an agent needs before calling is missing.

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% for the single `url` parameter, including the https requirement and the A2A card path. The description reinforces that the URL can point at either a paid endpoint or an agent card, but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: it checks an x402 endpoint for Bazaar indexing, validating the 402 PAYMENT-REQUIRED header, discovery metadata, schemas, description limits and service name. It also explicitly covers a second scope (A2A agent cards), so an agent can tell exactly what the tool inspects without opening the schema.

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?

Gives an explicit trigger: 'Use when an agent needs to lint an x402 listing or A2A agent card before its first sale.' That is clear when-to-use context, but there are no stated exclusions or named alternatives among the many siblings, 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.