Skip to main content
Glama

makememoneynomistakes.ai: ERC-8004 agent reputation and fraud checks

by ai.makememoneynomistakes
OverviewDiscussionsAdmin

Open Commerce Pathways: ledger

pathways_ledger
Read-only

Step 6 of Open Commerce Pathways: the real money in and out of the wallet that paid for your x402 compute runs, from Base USDC transfers we scan onchain since its first run. Income counts only x402 (EIP-3009) payments to that wallet; plain transfers in are deposits. Spend is split into our fees, route sellers and other. profit is true only when coverage is current and income exceeds spend. Free within the per-IP allowance, then $0.002. Live data only.

Input Schema

NameRequiredDescriptionDefault
walletYesThe address that paid for a pathway session or compute run.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / anyOf
      Previous value: -[
-  {
-    "properties": {
-      "coverage": {
-        "properties": {
-          "current": {
-            "type": "boolean"
-          }
-        },
-        "required": [
-          "current"
-        ],
-        "type": "object"
-      },
-      "deposits_usdc": {
-        "type": "string"
-      },
-      "income": {
-        "type": "object"
-      },
-      "items": {
-        "type": "array"
-      },
-      "net_usdc": {
-        "type": "string"
-      },
-      "note": {
-        "type": "string"
-      },
-      "profit": {
-        "type": "boolean"
-      },
-      "spend": {
-        "type": "object"
-      },
-      "tracked_since": {
-        "type": "string"
-      },
-      "wallet": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "wallet",
-      "coverage",
-      "net_usdc",
-      "profit",
-      "note"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "accepts": {
-        "items": {
-          "properties": {
-            "amount": {
-              "type": "string"
-            },
-            "asset": {
-              "type": "string"
-            },
-            "network": {
-              "type": "string"
-            },
-            "payTo": {
-              "type": "string"
-            },
-            "scheme": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "scheme",
-            "network",
-            "amount",
-            "asset",
-            "payTo"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "error": {
-        "type": "string"
-      },
-      "resource": {
-        "properties": {
-          "url": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "url"
-        ],
-        "type": "object"
-      },
-      "x402Version": {
-        "const": 2,
-        "type": "integer"
-      }
-    },
-    "required": [
-      "x402Version",
-      "accepts"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "coverage": {
+        "properties": {
+          "current": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "current"
+        ],
+        "type": "object"
+      },
+      "deposits_usdc": {
+        "type": "string"
+      },
+      "income": {
+        "type": "object"
+      },
+      "items": {
+        "type": "array"
+      },
+      "net_usdc": {
+        "type": "string"
+      },
+      "note": {
+        "type": "string"
+      },
+      "page": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "profit": {
+        "type": "boolean"
+      },
+      "spend": {
+        "type": "object"
+      },
+      "tracked_since": {
+        "type": "string"
+      },
+      "wallet": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "wallet",
+      "coverage",
+      "net_usdc",
+      "profit",
+      "note"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "accepts": {
+        "items": {
+          "properties": {
+            "amount": {
+              "type": "string"
+            },
+            "asset": {
+              "type": "string"
+            },
+            "network": {
+              "type": "string"
+            },
+            "payTo": {
+              "type": "string"
+            },
+            "scheme": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "scheme",
+            "network",
+            "amount",
+            "asset",
+            "payTo"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "error": {
+        "type": "string"
+      },
+      "resource": {
+        "properties": {
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "url"
+        ],
+        "type": "object"
+      },
+      "x402Version": {
+        "const": 2,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "x402Version",
+      "accepts"
+    ],
+    "type": "object"
+  }
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / wallet / description
      Previous value: -"The address that paid for a pathway compute run."New value: +"The address that paid for a pathway session or compute run."
  3. Added

TDQS

A4/5.0
Behavior5/5

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

Goes well past the readOnlyHint by defining what counts as income (only EIP-3009 x402 payments; plain inbound transfers are treated as deposits), how spend is bucketed (fees, route sellers, other), the exact condition for profit=true (coverage current and income > spend), the data source (onchain Base USDC scans since first run), and 'Live data only' meaning no historical view. This is unusually rich disclosure for a read 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 essential framing, and the dense clauses (income definition, spend buckets, profit condition, pricing) each carry real information. It runs long and packs several distinct facts into single sentences, but nothing is filler.

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?

With an output schema present, the description needn't explain the return shape, and it still supplies everything an agent needs to interpret the result: the income/spend/profit definitions, the coverage caveat that can make profit false, the data freshness ('live only'), and the cost model.

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 coverage is 100% and the single wallet parameter already has a description, so the schema carries the burden. The description reinforces that the wallet is the one that paid for x402 compute runs, but adds no format or constraint 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?

Names a concrete resource (a wallet ledger of real money in/out) tied to a specific chain and asset (Base USDC) and a specific flow (x402 compute runs). The 'Step 6' framing situates it in a pipeline, though it never names the sibling that answers a similar accounting question (e.g. pathways_report), so differentiation relies on inference.

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 'Step 6 of Open Commerce Pathways' label implies when in the workflow to call it, and pricing ('free within per-IP allowance, then $0.002') tells the agent about cost. But there is no explicit when-not guidance and no named alternative for adjacent accounting needs among the many pathways_* siblings.

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

All makememoneynomistakes.ai: ERC-8004 agent reputation and fraud checks toolsInspect
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.

Resources