Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

pageaudit__sellersearch

Search the live x402 seller index (~11k endpoints): find paid APIs by keyword, price and chain. 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/pageaudit/sellersearch

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

Input Schema

NameRequiredDescriptionDefault
qNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / q
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / url
      Removed value: -{
-  "type": "string"
-}
  2. Changed2 schema fields changed
    • removedInput schema / properties / q
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / url
      Added value: +{
+  "type": "string"
+}
  3. Changed3 schema fields changed
    • addedInput schema / properties / q
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / sellers
      Removed value: -{
-  "description": "Comma-separated seller URLs (max 20)",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "sellers"
-]
  4. Changed3 schema fields changed
    • removedInput schema / properties / q
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / sellers
      Added value: +{
+  "description": "Comma-separated seller URLs (max 20)",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "sellers"
+]
  5. Changed2 schema fields changed
    • removedInput schema / properties / limit
      Removed value: -{
-  "type": "number"
-}
    • removedInput schema / properties / sort
      Removed value: -{
-  "type": "string"
-}
  6. Added

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningful work: it discloses the $0.01 USDC-on-Base cost, the exact payment slot (params._meta["x402/payment"]), the chain id (eip155:8453), and the HTTP endpoint. What it leaves out is the shape of results and any pagination or coverage limits on the ~11k index.

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, front-loaded sentences with no filler: purpose first, then cost/payment mechanics, then transport. The endpoint URL is long but earns its place for an agent that may call it directly.

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 one-optional-parameter search with no output schema and no annotations, the definition covers cost, payment mechanics, and endpoint, which is the hardest part to guess. It does not say what a hit looks like, how many results come back, or what happens when 'q' is omitted, leaving real gaps for a discovery tool.

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 the single optional 'q' parameter. The description gestures at 'by keyword', which helps, but it also advertises filtering by 'price and chain' that the schema does not expose, actively misleading the agent about what it can pass. That overclaim pulls the score below the baseline.

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 ('search the live x402 seller index, ~11k endpoints') and adds the domain purpose ('find paid APIs'). It is clearly distinguishable from siblings such as newsellers or trends, though the claim of filtering 'by keyword, price and chain' overstates what the tool surface suggests.

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?

Usage is implied by 'find paid APIs by keyword' — this is the discovery/discovery-search step. But there is no explicit when-to-use, when-not-to-use, or routing to siblings like shortlist, vet, or trends, so the agent must infer placement in a workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All automaton toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources