Wever Labs Agent Products

Agent File Desk Rail

wever_agent-file-desk-rail

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. Inspect supplied file bytes, compute content hashes, identify exact duplicates and report bounded content metadata. Operating boundary: Send inline file bytes in a supported format. The response includes content hashes, exact duplicates and metadata. The input schema lists size and format limits. POST /api/agent-file-desk-rail. 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "idempotency_key": "<idempotency_key>",
      "usage": "<usage>",
      "mode": "<mode>",
      "files": "<files>"
    },
    "name": "wever_agent-file-desk-rail"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	Yes
`files`	Yes
`usage`	Yes
`idempotency_key`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 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 / properties / files

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "content_base64": {
+        "maxLength": 43692,
+        "pattern": "^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=)?(?![\\s\\S])",
+        "type": "string"
+      },
+      "expected_sha256": {
+        "anyOf": [
+          {
+            "pattern": "^[a-f0-9]{64}(?![\\s\\S])",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "file_id": {
+        "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}(?![\\s\\S])",
+        "type": "string"
+      },
+      "name": {
+        "maxLength": 160,
+        "minLength": 1,
+        "pattern": "^[^/\\\\\\u0000-\\u001f\\u007f]+(?![\\s\\S])",
+        "type": "string"
+      }
+    },
+    "required": [
+      "file_id",
+      "name",
+      "content_base64",
+      "expected_sha256"
+    ],
+    "type": "object"
+  },
+  "maxItems": 16,
+  "minItems": 1,
+  "type": "array"
+}

addedInput schema / properties / idempotency_key

Added value: +{
+  "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}(?![\\s\\S])",
+  "type": "string"
+}

addedInput schema / properties / mode / const
```
Added value: +"inspect"
```
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 / usage

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

addedInput schema / required

Added value: +[
+  "idempotency_key",
+  "usage",
+  "mode",
+  "files"
+]

First observedSep 29, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Beyond the annotations it discloses pricing (0.10 USDC/call on Base), a 10-call 30-day free allowance, credential/mandate requirements, durable record creation and response contents — useful context for a destructiveHint=true, openWorldHint=true tool. However, it never reconciles the passive word 'inspect' with destructiveHint=true, and does not say whether duplicates are detected within the submitted batch or against previously stored records. No contradiction, but a residual ambiguity.

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?

Sentences are individually informative but the core purpose is buried after pricing and the trailing sentences ('This adapter grants no authority...', 'Existing product credentials... remain required where applicable') are generic boilerplate. Front-loading the operation would materially improve it.

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?

It compensates partly for the absent output schema by enumerating what the response contains, and covers auth and cost. But for a paid, destructive, four-required-parameter tool it leaves the usage enum, idempotency behavior, duplicate-detection scope and failure/refund behavior unspecified.

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 four required parameters, so the description must carry the load and largely does not. It hints at file bytes and mentions that the schema holds size/format limits, but says nothing about the synthetic vs operational usage enum, idempotency_key semantics, the mode constant, file_id, or expected_sha256's purpose.

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 second sentence gives a specific verb and resource chain: inspect file bytes, compute content hashes, identify exact duplicates, report metadata. That is far more precise than the title. It stops short of naming how it differs from neighboring rails such as wever_agent-decision-packet-rail or wever_atlas-asset-passport.

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?

The description supplies an input constraint (send inline file bytes in a supported format) but no when-to-use or when-not-to-use guidance relative to the ~50 sibling tools. The pointer to /api/operations-contract is an external reference rather than an in-definition routing rule.

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.