WarpPay402 Gateway

by com.warppay402.api

Overview Discussions Admin

This connector has been deprecated

I used the same url for two different postings.

arc_dex_oracle

Read-only

Real-time ETH/USDC spot price resolver and DEX oracle for Arc Mainnet ($0.001 USDC)

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

Input Schema

Name	Required	Description	Default
`pair`	No	Trading pair ticker symbol to resolve	ETH/USDC

Output Schema

Name	Required	Description
`pair`	No	Queried ticker pair
`price`	Yes	Spot price in USD
`success`	Yes	Resolution status
`timestamp`	No	ISO price timestamp

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 25, 2026

addedInput schema / properties / pair / description

Added value: +"Trading pair ticker symbol to resolve"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "pair": {
+      "description": "Queried ticker pair",
+      "type": "string"
+    },
+    "price": {
+      "description": "Spot price in USD",
+      "type": "number"
+    },
+    "success": {
+      "description": "Resolution status",
+      "type": "boolean"
+    },
+    "timestamp": {
+      "description": "ISO price timestamp",
+      "type": "string"
+    }
+  },
+  "required": [
+    "success",
+    "price"
+  ],
+  "type": "object"
+}

AddedSep 20, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, openWorld and non-destructive, so safety is covered; the description usefully adds the Arc Mainnet network and the $0.001 USDC call cost, which is real behavioral context. It does not disclose price freshness/update cadence or any rate limits, so it stops at a 3.

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 front-loaded sentence with the core identity first and the cost parenthetical last. No filler, though it is a single bare sentence with no elaboration.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. However, for an oracle tool in a crowded sibling set, the description omits which pairs are usable and when to route here versus other price sources.

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 'pair' parameter, so the schema already explains it. The description's 'ETH/USDC' merely echoes the default value and adds no syntax or supported-pair-range detail beyond the schema.

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 states a specific verb+resource ('spot price resolver and DEX oracle') and scopes it to ETH/USDC on Arc Mainnet, which distinguishes it from forex_oracle and the network oracles. It stops short of explicitly naming which sibling to prefer, so it's clear but not fully differentiated.

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 when-to-use or when-not-to-use guidance despite several competing oracle/tool siblings (forex_oracle, arc_network_oracle_query, data_feeds, public_data_feed). Usage is only implied by the 'ETH/USDC' scoping in the text.

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

All WarpPay402 Gateway tools Inspect

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

Need Help?