Wever Labs Agentic Rails

Support brief

wever_support-brief

Read-only

DiligenceOps: submit one support conversation excerpt, as a chat, email thread or ticket. The signed brief states who speaks for support and who is the customer, the issue raised, the current status, every promise support made with its amount and deadline, and the stated next step with who owns it, each quoted. POST /api/support-brief. Reads only the material in the call: no page fetch, no account access, no merchant contact and no money movement. 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. The report matches words, figures, dates and named items between the submitted texts; it does not interpret meaning beyond that matching. Contract: /api/diligence-vendor-contract. Human page: https://weverlabs.com/diligence-checks/.

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": {
      "text": "<text>"
    },
    "name": "wever_support-brief"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	One support conversation excerpt: chat, email thread or ticket, up to 256 KB.
`label`	No	Optional name for the conversation, recorded in the brief.
`format`	No	html reduces the markup to readable text first. Defaults to html when the text starts with a tag, otherwise text.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Adds substantial behavior beyond the annotations: the tool is paid at 0.10 USDC per call on Base via x402 exact with 10 free signed-wallet calls per rolling 30 days, requires X-Wever-Wallet-Proof bound to the exact JSON arguments and route, and returns a report with an Ed25519 signed receipt. It also discloses the matching semantics ('matches words, figures, dates and named items... does not interpret meaning beyond that matching'), which is real expectation-setting. It stops short of describing what happens on payment failure or how a partially-matching excerpt is reported.

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?

Purpose and brief contents are front-loaded, then payment, auth binding, return shape, and semantics in a logical order. The prose is dense rather than bloated, though the trailing contract path, human page URL, and repeated signature/payment caveats add some tail weight that could be consolidated.

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?

There is no output schema, so the description carries the return contract itself, enumerating the brief's fields and the Ed25519 signed receipt, and it also covers pricing, free-tier limits, and wallet-proof binding. For a paid, non-idempotent, single-input tool, nothing material an agent needs before calling is missing.

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%, so all three parameters are already documented, including the format default heuristic and the 256 KB text limit. The description reinforces that the input is a single connective excerpt and that the label lands in the brief, but adds no syntax or edge-case detail about the parameters beyond what the schema states.

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 one support conversation excerpt, as a chat, email thread or ticket') plus the exact artifact produced (a signed brief naming speaker roles, issue, status, promises with amounts and deadlines, and next step). Among many sibling 'brief' tools, the support-conversation domain makes the distinction unambiguous.

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?

Usage context is implied by the required single excerpt and the enumerated brief contents, and the scope limits ('no page fetch, no account access, no merchant contact and no money movement') clarify what the tool will not do. However, no sibling or alternative is named, so an agent must infer selection from domain alone rather than from explicit when/when-not routing.

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?