Wever Labs Agent Products

Agent Permission Ledger

wever_agent-permission-ledger

Destructive

Paid URL: 0.10 USDC per call on Base; 10 signed-wallet free calls shared over rolling 30 days. Read the backend 402 body for x402 terms. Persist wallet-scoped permission grants and revocations and evaluate an exact subject, action and resource against those records. Operating boundary: Authenticated owner declarations within this ledger. Target systems must enforce resource access. No spending authority or external permission verification. POST /api/agent-permission-ledger. Existing product credentials, signed mandates, and single-use action grants remain required where applicable. This adapter grants no authority and never supplies server credentials. Wallet-authenticated bounded operations service with durable records. See /api/operations-contract for exact schemas, verified scope and unavailable capabilities.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	Yes
`limit`	No
`usage`	No
`action`	No
`offset`	No
`reason`	No
`actions`	No
`grant_id`	No
`resource`	No
`resources`	No
`expires_at`	No
`subject_wallet`	No
`idempotency_key`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedOct 3, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

removedInput schema / description

Removed value: -"The existing product POST body. Supply its documented mode, arguments, and required signed authority or grant. The product validates its full contract."

removedInput schema / maxProperties
```
Removed value: -64
```
removedInput schema / minProperties
```
Removed value: -1
```

addedInput schema / oneOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "actions": {
+        "items": {
+          "maxLength": 96,
+          "minLength": 1,
+          "type": "string"
+        },
+        "maxItems": 16,
+        "minItems": 1,
+        "type": "array",
+        "uniqueItems": true
+      },
+      "expires_at": {
+        "maximum": 4102444800,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "idempotency_key": {
+        "pattern": "^[a-zA-Z0-9_-]{1,96}(?![\\s\\S])",
+        "type": "string"
+      },
+      "mode": {
+        "const": "grant"
+      },
+      "resources": {
+        "items": {
+          "maxLength": 512,
+          "minLength": 1,
+          "type": "string"
+        },
+        "maxItems": 16,
+        "minItems": 1,
+        "type": "array",
+        "uniqueItems": true
+      },
+      "subject_wallet": {
+        "pattern": "^0x(?!0{40})[a-fA-F0-9]{40}(?![\\s\\S])",
+        "type": "string"
+      },
+      "usage": {
+        "enum": [
+          "synthetic",
+          "operational"
+        ]
+      }
+    },
+    "required": [
+      "mode",
+      "idempotency_key",
+      "subject_wallet",
+      "actions",
+      "resources",
+      "expires_at",
+      "usage"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "grant_id": {
+        "pattern": "^[a-f0-9]{64}(?![\\s\\S])",
+        "type": "string"
+      },
+      "idempotency_key": {
+        "pattern": "^[a-zA-Z0-9_-]{1,96}(?![\\s\\S])",
+        "type": "string"
+      },
+      "mode": {
+        "const": "revoke"
+      },
+      "reason": {
+        "maxLength": 512,
+        "minLength": 1,
+        "type": "string"
+      },
+      "usage": {
+        "enum": [
+          "synthetic",
+          "operational"
+        ]
+      }
+    },
+    "required": [
+      "mode",
+      "idempotency_key",
+      "grant_id",
+      "reason",
+      "usage"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "action": {
+        "maxLength": 96,
+        "minLength": 1,
+        "type": "string"
+      },
+      "mode": {
+        "const": "evaluate"
+      },
+      "resource": {
+        "maxLength": 512,
+        "minLength": 1,
+        "type": "string"
+      },
+      "subject_wallet": {
+        "pattern": "^0x(?!0{40})[a-fA-F0-9]{40}(?![\\s\\S])",
+        "type": "string"
+      }
+    },
+    "required": [
+      "mode",
+      "subject_wallet",
+      "action",
+      "resource"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "limit": {
+        "maximum": 25,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "mode": {
+        "const": "list"
+      },
+      "offset": {
+        "maximum": 255,
+        "minimum": 0,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "mode",
+      "offset",
+      "limit"
+    ],
+    "type": "object"
+  }
+]

addedInput schema / properties / action

Added value: +{
+  "maxLength": 96,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / actions

Added value: +{
+  "items": {
+    "maxLength": 96,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 16,
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}

addedInput schema / properties / expires_at

Added value: +{
+  "maximum": 4102444800,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / grant_id

Added value: +{
+  "pattern": "^[a-f0-9]{64}(?![\\s\\S])",
+  "type": "string"
+}

addedInput schema / properties / idempotency_key

Added value: +{
+  "pattern": "^[a-zA-Z0-9_-]{1,96}(?![\\s\\S])",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "maximum": 25,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / mode / enum

Added value: +[
+  "grant",
+  "revoke",
+  "evaluate",
+  "list"
+]

removedInput schema / properties / mode / maxLength
```
Removed value: -128
```
removedInput schema / properties / mode / minLength
```
Removed value: -1
```
removedInput schema / properties / mode / type
```
Removed value: -"string"
```

addedInput schema / properties / offset

Added value: +{
+  "maximum": 255,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / reason

Added value: +{
+  "maxLength": 512,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / resource

Added value: +{
+  "maxLength": 512,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / resources

Added value: +{
+  "items": {
+    "maxLength": 512,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 16,
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}

addedInput schema / properties / subject_wallet

Added value: +{
+  "pattern": "^0x(?!0{40})[a-fA-F0-9]{40}(?![\\s\\S])",
+  "type": "string"
+}

addedInput schema / properties / usage

Added value: +{
+  "enum": [
+    "synthetic",
+    "operational"
+  ]
+}

addedInput schema / required
```
Added value: +[
+  "mode"
+]
```

First observedSep 29, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds genuinely useful context beyond them: it grants no spending authority, performs no external permission verification, never supplies server credentials, and defers enforcement to target systems. Pricing and free-call quota are also disclosed. It does not, however, explain what a revoke destroys or whether expired grants are retained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence front-loads pricing and free-call details before the tool's actual function, and the body is a dense run-on string of clauses. Much of it is load-bearing (boundaries, auth requirements), but the ordering buries the purpose and the structure is hard to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter, four-mode tool with no output schema, the description omits mode-specific behavior, the list/evaluate return semantics, and nearly all parameter meaning. It compensates partially with solid operating-boundary statements, but an agent cannot invoke the modes correctly from this alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 13 parameters, so the description must carry the semantic load, and it largely does not. It never explains idempotency_key, expires_at, the synthetic/operational usage enum, grant_id formatting, or offset/limit, and the 'list' mode is not even mentioned as a capability. Only the high-level grant/revoke/evaluate concepts are conveyed.

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 pair: persisting wallet-scoped permission grants/revocations and evaluating a subject/action/resource against those records. That distinguishes it reasonably well from siblings like wever_agent-budget-guard or wever_payment-authority-inspector. The payment/pricing preamble pushes the core purpose into the second sentence, but the purpose itself is clear.

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?

It states prerequisites ('Existing product credentials, signed mandates, and single-use action grants remain required') and a boundary ('Target systems must enforce resource access'), which implies context. However, it never says when to use this versus the many overlapping siblings (delegated-authority, payment-authority-inspector, trust-scorecard), nor which mode is appropriate for which situation.

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

All Wever Labs Agent Products 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.

Agent Permission Ledger

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources