Wever Labs Agentic Rails

Settlement proof check

wever_settlement-proof-check

Read-only

Agent Access: submit a settlement claim (transaction reference, amount, asset, destination, network, what the claim rests on, whether delivery was made against it), the chain evidence read for it, each reading with its source, whether that source stands outside the seller and its facilitator, whether it found the transaction, its status (success, reverted, pending or dropped), the amount, asset, destination, network, confirmations, finality and when it was read, and the confirmations the receiver requires. The signed report says whether the transaction exists, is final and matches the claim field by field, and names every claim whose only proof is the seller’s own receipt, record or facilitator response, every settlement that reverted or was dropped after an earlier success, and every delivery made before finality. Two records agreeing with each other are wever_settlement-reconciliation-check, an invoice against a payment record is wever_invoice-payment-match and proof of a code change is wever_change-proof-check. Verdict settlement_failed, self_attested, settlement_unverified or settlement_proven. POST /api/settlement-proof-check. Reads only the material in the call: no network request, fetch, money movement, message, sharing, configuration change or external write. Paid URL: 0.10 USDC per call on Base via x402 exact, with the shared 10 signed-wallet free calls per rolling 30 days. Bind X-Wever-Wallet-Proof to the exact JSON arguments and the tool route. Returns a report with an Ed25519 signed receipt. Contract: /api/agent-access-contract. Human page: https://weverlabs.com/agent-access/.

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": {
      "claim": "<claim>"
    },
    "name": "wever_settlement-proof-check"
  }
}

Input Schema

Name	Required	Description
`claim`	Yes
`label`	No	Optional name recorded in the report.
`evidence`	No	Chain evidence read for the claim, in the order it was read.
`finality`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces this with 'no network request, fetch, money movement, message, sharing, configuration change or external write.' It adds payment terms (0.10 USDC per call on Base via x402, 10 free signed-wallet calls per 30 days), the X-Wever-Wallet-Proof binding requirement, and the Ed25519 signed receipt return, all beyond what annotations provide.

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?

Front-loaded with 'Agent Access: submit a settlement claim' and logically ordered, but the core is one very long run-on sentence enumerating fields, which is dense and hard to scan. The information earns its place, but the structure could be broken into clearer segments.

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?

For a complex nested-input tool with no output schema, the description covers inputs, report contents, verdicts, payment, auth, and read-only behavior. It is nearly complete; only minor gaps remain around the optional label and finality.confirmations semantics.

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

Parameters4/5

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

With 50% schema coverage and nested objects, the description compensates well by enumerating claim fields (reference, amount, asset, destination, network, proof basis, delivered) and evidence fields (source, independence, found, status, confirmations, finality, observed time). It adds meaning beyond the schema, though it does not clarify the label or finality.confirmations parameters explicitly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: submit a settlement claim and produce a signed report on whether the transaction exists, is final, and matches the claim field by field. It explicitly distinguishes itself from three named siblings (reconciliation-check, invoice-payment-match, change-proof-check), so an agent can route without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: two records agreeing is reconciliation-check, invoice vs payment record is invoice-payment-match, code-change proof is change-proof-check. It also names the verdict set (settlement_failed, self_attested, settlement_unverified, settlement_proven), which tells the agent what outcome space to expect.

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

All Wever Labs Agentic Rails 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.

Resources

Need Help?