Skip to main content
Glama

Oblique Markets

by markets.oblique.api

agent_preflight_bundle

Select up to five proven time, Base, wallet-balance and x402 verification utilities in one preflight bundle with statuses, evidence hash and bundle ID. $0.005/call via x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletYesBase/EVM wallet address to inspect
includeNoCompatibility alias for components
chain_idNoCompatibility chain identifier
endpointsNoCompatibility list; first URL is used by endpoint_verify
componentsNoUtilities to run; defaults to all five
endpoint_urlNoHTTPS x402 endpoint for endpoint_verify
wallet_addressNoCompatibility alias for wallet
endpoint_requestNoOptional request descriptor for endpoint_verify

Schema Changelog

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

  1. Changed10 schema fields changed
    • addedInput schema / properties / chain_id
      Added value: +{
+  "description": "Compatibility chain identifier",
+  "type": [
+    "string",
+    "integer"
+  ]
+}
    • addedInput schema / properties / components
      Added value: +{
+  "description": "Utilities to run; defaults to all five",
+  "items": {
+    "enum": [
+      "time",
+      "block_number",
+      "gas_price",
+      "usdc_balance",
+      "endpoint_verify"
+    ],
+    "type": "string"
+  },
+  "maxItems": 5,
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}
    • addedInput schema / properties / endpoint_request
      Added value: +{
+  "description": "Optional request descriptor for endpoint_verify",
+  "type": "object"
+}
    • addedInput schema / properties / endpoint_url
      Added value: +{
+  "description": "HTTPS x402 endpoint for endpoint_verify",
+  "format": "uri",
+  "type": "string"
+}
    • changedInput schema / properties / endpoints / description
      Previous value: -"Optional x402 endpoints to verify before spending"New value: +"Compatibility list; first URL is used by endpoint_verify"
    • removedInput schema / properties / endpoints / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / endpoints / items / properties
      Removed value: -{
-  "method": {
-    "default": "GET",
-    "enum": [
-      "GET",
-      "POST"
-    ],
-    "type": "string"
-  },
-  "url": {
-    "description": "HTTPS endpoint URL",
-    "format": "uri",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / endpoints / items / required
      Removed value: -[
-  "url"
-]
    • addedInput schema / properties / include
      Added value: +{
+  "description": "Compatibility alias for components",
+  "items": {
+    "enum": [
+      "time",
+      "block_number",
+      "gas_price",
+      "usdc_balance",
+      "endpoint_verify"
+    ],
+    "type": "string"
+  },
+  "maxItems": 5,
+  "type": "array",
+  "uniqueItems": true
+}
    • addedInput schema / properties / wallet_address
      Added value: +{
+  "description": "Compatibility alias for wallet",
+  "pattern": "^0x[0-9a-fA-F]{40}$",
+  "type": "string"
+}
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the behavioral disclosure burden. It does add useful context: the call costs $0.005 via x402 and the response yields statuses, an evidence hash, and a bundle ID. However, it does not disclose whether the operation is read-only, how endpoint_verify executes, whether defaults apply, or any authentication/rate-limit constraints.

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?

The description is a single, front-loaded sentence with no significant wasted words. The word 'proven' is mild promotional fluff, but the core behavior, scope, outputs, and pricing are all present.

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?

The tool has eight parameters, one nested object parameter, and no output schema. The description names the top-level outputs but not their structure or the default behavior of running all components. The schema covers parameter meanings well, but the description alone does not fully specify how the bundle behaves for an agent.

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%, so the parameters are already documented in the input schema. The description adds only the 'up to five' selection constraint and the general output shape, not new semantic meaning for individual parameters.

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?

The description names a specific action: selecting up to five time, Base, wallet-balance, and x402 verification utilities into a single preflight bundle, and lists key outputs (statuses, evidence hash, bundle ID). It reads as a bundle tool, which distinguishes it from individual sibling utilities, though it never explicitly names those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus the individual base_block_number, base_usdc_balance, server_time, x402_endpoint_verify, or b402_preflight siblings. The bundling phrasing implies an aggregation use case, but no explicit when/when-not or alternative routing is provided.

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.

TDQS

C2.7/5.0
Disambiguation1/5

Several tool groups are nearly indistinguishable: wallet_analyze, wallet_spy, and base_wallet_profile all inspect wallets; batch_extract, batch_url_json, and x401_batch_extract all batch-extract URLs; route_task, agentcore_route, and mpp_route all perform routing. An agent would need to read very carefully to avoid selecting the wrong tool.

Naming Consistency2/5

All names are snake_case, but there is no consistent verb_noun or namespace pattern: many are noun-only (inference, echo, sentiment, server_time), some are prefixed by domain (bazaar_, base_, x402_, rep_), and action prefixes vary widely (fetch_, compile_, extract_, purchase_, route_). The naming is readable but not predictable across the set.

Tool Count1/5

Seventy tools is an extremely large surface for an agent to choose from, and most appear to be independent paid service wrappers. This exceeds the 50+ extreme mismatch threshold in the calibration and creates an overwhelming selection problem.

Completeness4/5

Relative to its apparent purpose—exposing x402 payments and Bazaar market data—the coverage is extensive: diagnostics, preflight, settlement verification, receipt lookup, wallet checks, Bazaar analytics, web extraction, and text processing are all represented. The main gaps are operational side-effects like creating or updating a Bazaar listing, but those appear to be outside this read/purchase surface.

Resources