Anyway Possible Paid Agent Utilities

Base Wallet Readiness ($0.02 USDC)

treasury_preflight

Read-only

Check Base wallet readiness, ETH and USDC funding, gas, chain intent, destination type, and common payment hazards before signing.

Input Schema

TableJSON Schema

Name	Required	Description
`address`	Yes	Base wallet address that will fund and sign the planned payment.
`expectedChainId`	No	Expected EVM chain ID; Anyway Possible currently supports Base mainnet 8453.
`minGasReserveEth`	No	Minimum ETH balance to preserve for Base gas after the payment.
`plannedSpendUsdc`	No	Planned USDC spend as a decimal string with up to six fractional digits.
`destinationAddress`	No	Optional expected recipient address to screen for destination hazards.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`eth`	Yes
`usdc`	Yes
`alerts`	Yes
`checks`	Yes
`address`	Yes
`chainId`	Yes
`network`	Yes
`decision`	Yes
`riskLevel`	Yes
`observedAt`	Yes
`blockNumber`	Yes
`limitations`	Yes
`safeToProceed`	Yes
`recommendedAction`	Yes
`destinationAddress`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedSep 9, 2026

addedInput schema / properties / address / description

Added value: +"Base wallet address that will fund and sign the planned payment."

removedInput schema / properties / destinationAddress / $ref
```
Removed value: -"#/properties/address"
```

addedInput schema / properties / destinationAddress / description

Added value: +"Optional expected recipient address to screen for destination hazards."

addedInput schema / properties / destinationAddress / pattern
```
Added value: +"^0x[a-fA-F0-9]{40}$"
```
addedInput schema / properties / destinationAddress / type
```
Added value: +"string"
```

addedInput schema / properties / expectedChainId / description

Added value: +"Expected EVM chain ID; Anyway Possible currently supports Base mainnet 8453."

addedInput schema / properties / minGasReserveEth / description

Added value: +"Minimum ETH balance to preserve for Base gas after the payment."

addedInput schema / properties / minGasReserveEth / pattern
```
Added value: +"^[0-9]+(\\.[0-9]{1,18})?$"
```

addedInput schema / properties / plannedSpendUsdc / description

Added value: +"Planned USDC spend as a decimal string with up to six fractional digits."

addedInput schema / properties / plannedSpendUsdc / pattern
```
Added value: +"^[0-9]+(\\.[0-9]{1,6})?$"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "address": {
+      "type": "string"
+    },
+    "alerts": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "blockNumber": {
+      "type": "integer"
+    },
+    "chainId": {
+      "type": "integer"
+    },
+    "checks": {
+      "items": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "decision": {
+      "enum": [
+        "safe_to_pay",
+        "needs_funding",
+        "needs_gas",
+        "review_destination",
+        "reject"
+      ],
+      "type": "string"
+    },
+    "destinationAddress": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "eth": {
+      "type": "string"
+    },
+    "limitations": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "network": {
+      "type": "string"
+    },
+    "observedAt": {
+      "type": "string"
+    },
+    "recommendedAction": {
+      "type": "string"
+    },
+    "riskLevel": {
+      "enum": [
+        "low",
+        "medium",
+        "high"
+      ],
+      "type": "string"
+    },
+    "safeToProceed": {
+      "type": "boolean"
+    },
+    "usdc": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "address",
+    "destinationAddress",
+    "network",
+    "chainId",
+    "safeToProceed",
+    "decision",
+    "riskLevel",
+    "recommendedAction",
+    "eth",
+    "usdc",
+    "checks",
+    "alerts",
+    "limitations",
+    "blockNumber",
+    "observedAt"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds value by listing the specific checks performed, but does not disclose any additional behavioral nuances like potential latency or the fact that it makes external RPC calls. Given the annotation coverage, this is adequate but not rich.

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 sentence that front-loads the action and lists the key checks without any redundancy or fluff. It is appropriately concise and structured for quick comprehension.

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?

Given the tool has an output schema (present per context signals), the description doesn't need to detail return values. It covers the purpose and the inputs well enough for an agent to decide when to call it. The absence of details about optional parameters is mitigated by the schema's thorough descriptions.

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 every parameter already has a clear explanation in the schema. The description's list of checks (funding, gas, etc.) roughly maps to the parameters, but it adds no extra semantic detail beyond what the schema already provides. This meets the baseline for high schema coverage.

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 clearly states the action ('Check') and the resource ('Base wallet readiness'), and enumerates specific aspects (ETH and USDC funding, gas, chain intent, destination type, payment hazards). It distinguishes itself from simpler tools like base_balance by focusing on a pre-signing readiness assessment, though it doesn't explicitly name alternatives.

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?

The phrase 'before signing' gives a clear temporal trigger for when to use this tool, but there is no explicit guidance on when not to use it or comparisons to sibling tools like payment_guard or base_balance. The usage context is implied rather than explicitly contrasted with alternatives.

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

All Anyway Possible Paid Agent Utilities 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.