Skip to main content
Glama
x402 Oracle MCP (Base USDC)

x402 Oracle MCP (Base USDC)

oracle_bazaar_rewrite

Generate or rewrite CDP Bazaar metadata to match buyer search phrases, with serviceName, description, tags, and first-index freeze warnings before settling a new SKU.

Instructions

Generate SEO-optimized CDP Bazaar metadata (serviceName <=32 chars, description <=500 chars, <=5 tags) front-loaded with buyer search phrases and first-index freeze warnings ($1.50 USDC on Base). Unpaid calls return 402 terms. Use this before settling a new SKU; for broader launch diffs use complete_oracle_task.

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

Input Schema

NameRequiredDescriptionDefault
buyer_phrasesNoOptional list of target buyer search queries to front-load into serviceName and description.
current_descriptionNoOptional existing Bazaar resource description to rewrite for higher buyer-query match.

Output Schema

NameRequiredDescriptionDefault
riskNoPricing threshold and catalog freeze risks.
agentNoMachine-ready object containing serviceName, description, and tags.
wisdomYesExplanation of CDP Bazaar ranking and first-index copy freeze.
verdictYesRewrite readiness and freeze-avoidance verdict.
implementation_promptNoPrompt to apply the updated Bazaar metadata cleanly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / buyer_phrases / description
      Added value: +"Optional list of target buyer search queries to front-load into serviceName and description."
    • addedInput schema / properties / buyer_phrases / items
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / current_description / description
      Added value: +"Optional existing Bazaar resource description to rewrite for higher buyer-query match."
    • changedInput schema / required
      Previous value: -[
      -  "current_description"
      -]New value: +[]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "agent": {
      +      "description": "Machine-ready object containing serviceName, description, and tags.",
      +      "type": "object"
      +    },
      +    "implementation_prompt": {
      +      "description": "Prompt to apply the updated Bazaar metadata cleanly.",
      +      "type": "string"
      +    },
      +    "risk": {
      +      "description": "Pricing threshold and catalog freeze risks.",
      +      "type": "string"
      +    },
      +    "verdict": {
      +      "description": "Rewrite readiness and freeze-avoidance verdict.",
      +      "type": "string"
      +    },
      +    "wisdom": {
      +      "description": "Explanation of CDP Bazaar ranking and first-index copy freeze.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "verdict",
      +    "wisdom"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations cover only the mutation/safety profile (readOnlyHint=false, destructiveHint=false). The description adds the things an agent actually needs: the $1.50 USDC-on-Base cost, a 402 payment-required response for unpaid calls, and the first-index freeze warning that makes timing matter. That is substantial behavior disclosed beyond structured fields.

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?

One dense sentence carries constraints, pricing, and failure mode, then usage routing follows. The heavy parenthetical stacking makes it slightly harder to scan, but virtually no sentence is wasted.

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?

With an output schema present, return values need not be described, and the description covers cost, failure behavior, output limits, and sibling routing. What remains thin is guidance on how many buyer phrases to supply or what happens on a partially matching rewrite, a minor gap for a 2-optional-param tool.

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 coverage is 100% and both parameters are optional, so the schema already explains buyer_phrases and current_description. The description reinforces intent ("front-loaded with buyer search phrases") but adds no syntax, formatting, or edge-case detail beyond what the schema provides.

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?

"Generate SEO-optimized CDP Bazaar metadata" is a specific verb+resource with concrete output constraints (serviceName <=32 chars, description <=500 chars, <=5 tags). It clearly distinguishes itself from complete_oracle_task by naming it as the broader-diff alternative.

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?

"Use this before settling a new SKU" gives an explicit trigger, and "for broader launch diffs use complete_oracle_task" routes to the alternative. No explicit statement of when not to use it (e.g., after a SKU is already live), which keeps it off a 5.

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