UNIALL RWA Index

Get index stats

get_index_stats

Read-onlyIdempotent

Returns aggregate UNIALL index counts for assets, verified assets, issuers, chains, deployments, and categories. Useful for a high-level snapshot of index coverage.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`facts`	Yes	Sourced scalar facts. Each item has field, value, source_url, source_type, as_of.
`answer`	Yes	Short natural-language summary of the result.
`assets`	No	Matched assets when applicable (find_assets). Empty or omitted for stats/summary tools.
`disclaimer`	Yes	Fixed data-only disclaimer; not investment advice.
`request_id`	Yes	Request correlation id.
`index_as_of`	Yes	ISO timestamp for index freshness.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "answer": {
+      "description": "Short natural-language summary of the result.",
+      "type": "string"
+    },
+    "assets": {
+      "description": "Matched assets when applicable (find_assets). Empty or omitted for stats/summary tools.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "aum_usd": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "category": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "chains": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "id": {
+            "type": "string"
+          },
+          "issuer": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "symbol": {
+            "type": "string"
+          },
+          "transfer_standard": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "uniall_url": {
+            "type": "string"
+          },
+          "verified": {
+            "type": "boolean"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "disclaimer": {
+      "description": "Fixed data-only disclaimer; not investment advice.",
+      "type": "string"
+    },
+    "facts": {
+      "description": "Sourced scalar facts. Each item has field, value, source_url, source_type, as_of.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "as_of": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "field": {
+            "type": "string"
+          },
+          "source_type": {
+            "type": "string"
+          },
+          "source_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "value": {}
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "index_as_of": {
+      "description": "ISO timestamp for index freshness.",
+      "type": "string"
+    },
+    "request_id": {
+      "description": "Request correlation id.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "answer",
+    "facts",
+    "disclaimer",
+    "index_as_of",
+    "request_id"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedNov 2, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedNov 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and idempotency profile is fully covered. The description adds no further behavioral context — nothing about freshness of the counts, caching, or cost — and the return shape is covered by the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what is returned and followed by the use case. No filler, no restatement of the title.

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?

With no parameters, an existing output schema and rich annotations, the description covers what an agent needs to select and invoke it. The only missing element is whether counts are live or cached, which matters for a stats tool but is not essential to invocation.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly does not invent parameter discussion.

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?

Names a specific verb ('Returns') and resource ('aggregate UNIALL index counts') and enumerates exactly which entity counts come back (assets, issuers, chains, deployments, categories). That enumeration implicitly separates it from find_assets and get_asset_summary, which operate on individual records, though no sibling is named 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?

'Useful for a high-level snapshot of index coverage' hints at the use case but gives no explicit when-to-use/when-not guidance and never names an alternative such as find_assets for per-asset detail. An agent can infer the role but must reason about it.

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

All UNIALL RWA Index 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?