Skip to main content
Glama

Oblique Markets

by markets.oblique.api
OverviewAdmin

reprice_regret

Did a price change on an x402 Bazaar listing pay off? Give one listing's resource_url or a seller_payto address (25 listings per page) and a window_days (7–90, default 30): replays the reported price history from daily snapshots, marks every repricing event with 30d calls and payers before and after it, computes each event's revenue counterfactual in USDC on the observed post-change volume with a one-line verdict, and compares against peers sharing the listing's first tag. Free example: GET /api/v1/reprice-regret/example. $0.01/call via x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoOpaque paging cursor from a previous seller_payto response.
networkNoOptional CAIP-2 network filter, e.g. 'eip155:8453' or 'solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpKuc147dw2N9d'.
window_daysNoHow many snapshot days back from the latest snapshot to replay (7–90, default 30).
resource_urlNoOne listing: the resource URL exactly as the x402 Bazaar reports it (http/https). Mutually exclusive with seller_payto.
seller_paytoNoAll listings paid to this address (the payTo the Bazaar reports); up to 25 per page with a cursor. Mutually exclusive with resource_url.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed8 schema fields changed
    • addedInput schema / description
      Added value: +"Exactly one of resource_url or seller_payto is required."
    • changedInput schema / examples
      Previous value: -[
-  {
-    "resource_url": "https://api.aidress.ai/pay/agent_funding_lonestaroracle_xyz"
-  }
-]New value: +[
+  {
+    "resource_url": "https://x402.shizu.me/crypto"
+  }
+]
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque paging cursor from a previous seller_payto response.",
+  "type": "string"
+}
    • changedInput schema / properties / resource_url / description
      Previous value: -"The listing resource URL exactly as the x402 Bazaar reports it (http/https)."New value: +"One listing: the resource URL exactly as the x402 Bazaar reports it (http/https). Mutually exclusive with seller_payto."
    • addedInput schema / properties / seller_payto
      Added value: +{
+  "description": "All listings paid to this address (the payTo the Bazaar reports); up to 25 per page with a cursor. Mutually exclusive with resource_url.",
+  "type": "string"
+}
    • removedInput schema / properties / since_date
      Removed value: -{
-  "description": "Optional ISO date (YYYY-MM-DD); only snapshots on or after this date are replayed.",
-  "type": "string"
-}
    • addedInput schema / properties / window_days
      Added value: +{
+  "default": 30,
+  "description": "How many snapshot days back from the latest snapshot to replay (7–90, default 30).",
+  "maximum": 90,
+  "minimum": 7,
+  "type": "integer"
+}
    • removedInput schema / required
      Removed value: -[
-  "resource_url"
-]
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and handles it well: it discloses that the tool replays snapshots, compares 30d calls/payers before and after each repricing, derives a counterfactual, and compares peer tags. It also discloses cost ($0.01/call via x402) and provides a free example endpoint, so an agent knows the operational and financial implications before calling.

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

Conciseness5/5

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

The description is a single dense sentence front-loaded with the motivating question and required inputs, followed by the analysis pipeline, cost, and example endpoint. Every clause earns its place; there is no filler or redundant restatement of the schema.

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?

No output schema exists, but the description compensates by specifying the computed outputs: per-event revenue counterfactual in USDC, a one-line verdict, and peer comparison. Combined with full schema coverage for parameters and the pricing/example details, an agent has enough to decide when and how to call this tool.

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 description coverage is 100%, so the baseline is 3, and the description still adds integration-level meaning: resource_url targets one listing, seller_payto targets up to 25 listings per page, and window_days controls the replay horizon. It reinforces the mutual-exclusivity of the selector parameters without simply repeating the schema.

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?

The description opens with a pointed question ('Did a price change... pay off?') and then specifies the exact analytical actions: replays price history from daily snapshots, marks repricing events, computes a USDC revenue counterfactual, and compares against peers. This clearly scopes the tool and differentiates it from sibling bazaar/x402 tools even without naming alternatives.

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?

It gives the exact invocation pattern: provide a resource_url or seller_payto address, plus an optional window_days, and clarifies that seller_payto results are paginated at 25 listings. It does not explicitly name alternatives or when-not-to-use cases, but the intended use case is unmistakable.

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

All Oblique Markets toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources