x402-data-gateway

Evaluate Agent Wallet Policy Conformance

wallet_policy_conformance

Evaluate safe standardized allow, deny, and error observations from an agent wallet or delegated signer. Use this after running a bounded provider policy test matrix to distinguish explicit provider-policy enforcement from validation or generic provider failures and to test exact execution shape separately from operation allowlisting. Accepts no credentials, wallet IDs, signatures, transactions, or raw provider responses; it evaluates caller-supplied observations and does not run the provider tests itself. Payment challenge and credentials are bound to POST https://agents.samedaydesk.com/security/wallet-policy-conformance, not mcp://. Retry the identical authorized arguments and credential.

Input Schema

Name	Required	Description
`network`	Yes	Network identifier used by the tested profile.
`protocol`	Yes	Payment or execution protocol bound by the tested profile.
`provider`	Yes	Wallet or delegated-signer provider name.
`profileId`	Yes	Caller-defined policy profile identifier with no credential or wallet secret.
`observations`	Yes	Unique standardized observations. Raw provider responses, signatures, transactions, credentials, and wallet IDs are rejected.

Output Schema

Name	Required	Description	Default
`product`	Yes
`profile`	Yes
`results`	Yes
`boundary`	Yes
`complete`	Yes
`decision`	Yes
`evaluatedAt`	Yes
`unsafeCases`	Yes
`schemaVersion`	Yes
`exactShapePassed`	Yes
`inconclusiveCases`	Yes
`missingRequiredCases`	Yes
`standardSchemaVersion`	Yes
`providerNativeVerified`	Yes
`providerNativeUnverified`	Yes
`notEvaluatedByWalletPolicy`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "boundary": {
+      "additionalProperties": false,
+      "properties": {
+        "credentialsAccepted": {
+          "const": false,
+          "type": "boolean"
+        },
+        "signatureVerified": {
+          "const": false,
+          "type": "boolean"
+        },
+        "statement": {
+          "type": "string"
+        },
+        "transactionBroadcast": {
+          "const": false,
+          "type": "boolean"
+        },
+        "walletAccessed": {
+          "const": false,
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "credentialsAccepted",
+        "walletAccessed",
+        "signatureVerified",
+        "transactionBroadcast",
+        "statement"
+      ],
+      "type": "object"
+    },
+    "complete": {
+      "type": "boolean"
+    },
+    "decision": {
+      "enum": [
+        "conformant",
+        "partial",
+        "unsafe"
+      ],
+      "type": "string"
+    },
+    "evaluatedAt": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "exactShapePassed": {
+      "type": "boolean"
+    },
+    "inconclusiveCases": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "missingRequiredCases": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "notEvaluatedByWalletPolicy": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "product": {
+      "const": "samedaydesk-wallet-policy-conformance",
+      "type": "string"
+    },
+    "profile": {
+      "additionalProperties": false,
+      "properties": {
+        "network": {
+          "type": "string"
+        },
+        "profileId": {
+          "type": "string"
+        },
+        "protocol": {
+          "type": "string"
+        },
+        "provider": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "profileId",
+        "provider",
+        "network",
+        "protocol"
+      ],
+      "type": "object"
+    },
+    "providerNativeUnverified": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "providerNativeVerified": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "actual": {
+            "enum": [
+              "allowed",
+              "denied",
+              "error"
+            ],
+            "type": "string"
+          },
+          "case": {
+            "enum": [
+              "intended",
+              "missing_authorization",
+              "wrong_operation",
+              "duplicate_approved_action",
+              "wrong_chain",
+              "wrong_token_contract_or_program",
+              "wrong_recipient",
+              "wrong_amount",
+              "wrong_function_or_instruction",
+              "wrong_route_or_offer",
+              "changed_protocol_challenge",
+              "replay_or_reuse",
+              "reordered_approved_actions",
+              "mixed_unapproved_action",
+              "wrong_fee_asset",
+              "missing_validity"
+            ],
+            "type": "string"
+          },
+          "code": {
+            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:/-]{0,63}$",
+            "type": "string"
+          },
+          "control": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "denialClass": {
+            "enum": [
+              "none",
+              "policy",
+              "validation",
+              "provider"
+            ],
+            "type": "string"
+          },
+          "expectationMet": {
+            "type": "boolean"
+          },
+          "expected": {
+            "enum": [
+              "allow",
+              "deny"
+            ],
+            "type": "string"
+          },
+          "finding": {
+            "enum": [
+              "expected_behavior",
+              "unsafe_allowed",
+              "expected_behavior_not_proven",
+              "denied_outside_provider_policy"
+            ],
+            "type": "string"
+          },
+          "providerNativeVerified": {
+            "type": "boolean"
+          },
+          "required": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "case",
+          "actual",
+          "denialClass",
+          "expected",
+          "control",
+          "required",
+          "expectationMet",
+          "providerNativeVerified",
+          "finding"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "schemaVersion": {
+      "const": "samedaydesk.wallet-policy-conformance.v1",
+      "type": "string"
+    },
+    "standardSchemaVersion": {
+      "const": "agent-payment-policy.wallet-policy-observation-report.v1",
+      "type": "string"
+    },
+    "unsafeCases": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "schemaVersion",
+    "standardSchemaVersion",
+    "product",
+    "evaluatedAt",
+    "profile",
+    "decision",
+    "complete",
+    "exactShapePassed",
+    "results",
+    "providerNativeVerified",
+    "providerNativeUnverified",
+    "notEvaluatedByWalletPolicy",
+    "missingRequiredCases",
+    "unsafeCases",
+    "inconclusiveCases",
+    "boundary"
+  ],
+  "type": "object"
+}

AddedAug 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses what is rejected (credentials, wallet IDs, signatures, transactions, raw provider responses), that it only evaluates caller-supplied observations, and adds payment/credential binding to a POST URL rather than mcp:// plus retry semantics. It stops short of describing rate limits or output behavior, but this is strong disclosure for an annotation-free tool.

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?

Front-loaded with the core action, then intent, input constraints, and transport/retry details in a compact sequence. Sentences are dense but every one carries information; no filler.

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?

An output schema exists, so return values need not be explained, and the description covers input constraints, the intended workflow placement, transport binding, and retry guidance. The one real gap is sibling differentiation against stateful_wallet_policy_conformance, which is relevant given how close the names are.

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 schema already documents all five parameters, including the nested observation fields. The description reinforces input constraints (no credentials/wallet IDs/raw responses) and the observation-standardization intent but adds no field-level syntax or format beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource: evaluate standardized allow/deny/error observations from an agent wallet or delegated signer. Clear and concrete, but it never distinguishes itself from the near-identically-named sibling 'stateful_wallet_policy_conformance', so an agent cannot route between the two from this text alone.

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?

Gives explicit context: use it after running a bounded provider policy test matrix, to separate provider-policy enforcement from validation/generic failures and to test execution shape vs. operation allowlisting. It also flags a boundary ('does not run the provider tests itself'), but names no alternative tool, leaving the sibling ambiguity unresolved.

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

All x402-data-gateway tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.