Wever Labs Agent Products

Atlas asset search

wever_atlas-asset-search

Read-only

Search covered tokenized assets by literal text, category, stage or six rights filters and return paginated summaries with stage and rights. Empty arguments list all covered assets within the result limit. Reads the versioned Atlas reference dataset, not live market quotes. Each result preserves source dates and labels for provisional or unverified historical display data. POST /api/atlas-asset-search. Paid URL: 0.10 USDC per call on Base mainnet using x402 exact, under the existing shared 10 signed-wallet free calls over rolling 30 days. X-Wever-Wallet-Proof must bind to the exact JSON arguments and this API path, not /mcp. The adapter forwards only caller-supplied proof and payment headers. Authority is read-only: no dataset or external writes, asset trading, autonomous source fetches, spending authority or publication. API access billing is separate: it records free usage or settles an explicit caller-supplied payment authorization. Read /api/atlas-contract and the backend 402 body for exact schemas and billing terms.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wever_atlas-asset-search"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`query`	No	Case-insensitive literal text search over sourced asset fields. Combined with category when both are supplied.
`stage`	No	Exact taxonomy stage: 1 wrapper, 2 issuer-sponsored, 3 native issuance. All supplied filters are combined.
`offset`	No
`rights`	No	Combine disclosed rights filters. Enumerated values match exactly. not disclosed matches missing public disclosure, not a negative right.
`category`	No	Case-insensitive exact category id or label from the dataset.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

addedInput schema / properties / rights

Added value: +{
+  "additionalProperties": false,
+  "description": "Combine disclosed rights filters. Enumerated values match exactly. not disclosed matches missing public disclosure, not a negative right.",
+  "minProperties": 1,
+  "properties": {
+    "custody_backing": {
+      "description": "Case-insensitive literal substring in the disclosed backing and custodian description. Use not disclosed for an undisclosed value.",
+      "maxLength": 256,
+      "minLength": 1,
+      "pattern": "\\S",
+      "type": "string"
+    },
+    "distributions": {
+      "enum": [
+        "passed through",
+        "not passed through",
+        "not disclosed"
+      ],
+      "type": "string"
+    },
+    "issuer_involvement": {
+      "enum": [
+        "sponsored by the issuer",
+        "not sponsored",
+        "not disclosed"
+      ],
+      "type": "string"
+    },
+    "legal_status": {
+      "enum": [
+        "owner of record",
+        "economic exposure only",
+        "not disclosed"
+      ],
+      "type": "string"
+    },
+    "redemption": {
+      "enum": [
+        "redeemable for the underlying",
+        "not redeemable for the underlying",
+        "not disclosed"
+      ],
+      "type": "string"
+    },
+    "voting": {
+      "enum": [
+        "holder votes",
+        "votes with management",
+        "none",
+        "not disclosed"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / stage

Added value: +{
+  "description": "Exact taxonomy stage: 1 wrapper, 2 issuer-sponsored, 3 native issuance. All supplied filters are combined.",
+  "enum": [
+    1,
+    2,
+    3
+  ],
+  "type": "integer"
+}

AddedOct 5, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Far exceeds the annotations: it discloses cost (0.10 USDC per call on Base mainnet via x402 exact), the 10 free signed-wallet calls per rolling 30 days, the exact proof-binding requirement (X-Wever-Wallet-Proof bound to the JSON arguments and this path, not /mcp), and what the adapter does and does not forward. It also flags data freshness semantics ('source dates and labels for provisional or unverified historical display data') and enumerates the authority boundary (no writes, trading, autonomous fetches, spending, or publication).

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 behavior are correctly front-loaded, but the definition runs long and the closing billing/authority block partially restates the paid-URL sentence ('records free usage or settles an explicit caller-supplied payment authorization' vs the free-call/pricing line earlier). The compliance enumeration ('no dataset or external writes, asset trading, autonomous source fetches, spending authority or publication') is verbose for a read-only search.

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?

With no output schema, the description still tells the agent what comes back (paginated summaries with stage and rights, preserving source dates and provisional/unverified labels). It also covers cost, auth header binding, and where to find exact schemas and billing terms (atlas-contract, backend 402 body), leaving no operational gap for a read-only, paid, open-world search.

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?

At 67% schema description coverage, the schema already carries the meaningful param docs, including the enum semantics for stage and the rights sub-properties. The description adds the count of rights filters ('six') and notes that filters combine, but supplies no extra syntax, format, or interaction detail for limit/offset or the default-arg behavior beyond what is already visible.

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?

Opens with a specific verb and resource ('Search covered tokenized assets') and enumerates the exact filter dimensions (literal text, category, stage, six rights filters), then states the return shape ('paginated summaries with stage and rights'). It separates itself from live-quote tools, but does not distinguish itself from the closely named sibling wever_atlas-asset-passport, leaving one obvious identity ambiguity.

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 gives one concrete usage case — 'Empty arguments list all covered assets within the result limit' — but no routing guidance against alternatives, notably when to use this search versus the single-asset atlas-asset-passport endpoint. The 'not live market quotes' line clarifies the data source rather than tool selection.

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.