Wever Labs Agentic Rails

Atlas stage brief

wever_atlas-stage-brief

Read-only

Atlas evidence: submit one Atlas stage: wrapper, issuer-sponsored or native. The signed brief lists every asset the published dataset classifies at that stage with its classification basis and the six rights fields (issuer involvement, custody and backing, distributions, voting, legal status, redemption), each marked disclosed or not disclosed, with per-field and total counts beside the catalog stage count. A stage with no assets returns a signed brief with an asset count of 0. POST /api/atlas-stage-brief. Reads the published Tokenization Atlas dataset at https://atlas.weverlabs.com/api/assets once per call, the same read the Atlas evidence tools make, with no dataset writes and no issuer contact. Every report names the dataset version it read, and a field the dataset does not hold is reported as not in the published dataset. 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/atlas-board-contract. Human page: https://atlas.weverlabs.com/.

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": {
      "stage": "<stage>"
    },
    "name": "wever_atlas-stage-brief"
  }
}

Input Schema

Name	Required	Description	Default
`stage`	Yes	One Atlas taxonomy stage: wrapper (stage 1), issuer-sponsored (stage 2) or native (stage 3, native issuance).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Well beyond the annotations, the description discloses that each call performs a single read of the published dataset with no dataset writes and no issuer contact, that the response is an Ed25519 signed receipt naming the dataset version, that missing fields are reported rather than fabricated, and the zero-asset edge case. It also spells out the payment model (0.10 USDC via x402 exact on Base, 10 free signed-wallet calls per rolling 30 days) and the X-Wever-Wallet-Proof binding requirement — operational facts an agent cannot infer from readOnlyHint alone.

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?

Purpose and output shape are front-loaded, which is good, but the body is a dense run-on that mixes result semantics, payment rails, auth binding, and two links into one paragraph. The POST route, contract path, and human page are marginally useful boilerplate rather than decision-relevant content.

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?

For a one-parameter read tool with no output schema, the definition covers everything an agent needs: what the report contains (per-field disclosed flags, six rights fields, per-field and total counts), the dataset version stamp, the empty-result behavior, and the paid-call and wallet-proof prerequisites. Little is left ambiguous before invocation.

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 description coverage is 100% and the single enum parameter already documents its three values with stage numbers, so the schema does the heavy lifting. The description reinforces the semantics by explaining that the value selects which set of assets the brief enumerates and that its result is compared against the catalog stage count, but adds no format or validation detail beyond that.

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 names a specific verb and resource: submit one stage (wrapper, issuer-sponsored, native) and receive a signed brief listing every asset the published dataset classifies at that stage, with classification basis and six rights fields. That is far more specific than the title alone, and the stage-scoped framing implicitly distinguishes it from the issuer- and market-oriented Atlas siblings, though it never names an alternative explicitly.

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 rather than stated: the tool covers a taxonomy stage, returns an empty brief with asset count 0 when no assets exist, and reports absent fields as 'not in the published dataset.' There is no explicit when-to-use versus when-not guidance and no named alternative (e.g. atlas-issuer-brief, atlas-market-brief) to route an agent that actually wants a different slice.

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?