UNIALL RWA Index

Get asset summary

get_asset_summary

Read-onlyIdempotent

Returns a sourced fact sheet for one UNIALL asset by id, including missing_fields and unsourced_fields. Verified legal_entity / issuer_jurisdiction / issuer include source_url and evidence when the verification system has them; otherwise source_url is null and the field is listed in unsourced_fields. Useful when you need citable fields for a single asset without inventing data.

Input Schema

Name	Required	Description	Default
`id`	Yes	UNIALL asset id from find_assets results

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.

Changed2 schema fields changedNov 2, 2026

changedInput schema / properties / id / description

Previous value: -"UNIALL asset id (cuid)."New value: +"UNIALL asset id from find_assets results"

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"
+}

Changed3 schema fields changedNov 2, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / properties / id / description
```
Added value: +"UNIALL asset id (cuid)."
```
- removedInput schema / properties / id / minLength
```
Removed value: -1
```
First observedNov 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the description only needs to add behavioral context beyond that, and it does: it explains the null-vs-populated behavior of source_url and how unverified fields surface in unsourced_fields. It omits what happens for an unknown id or whether missing_fields is always present, which keeps it below a 5.

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?

Three sentences, front-loaded with the return contract before the sourcing caveat and the use case. Dense and largely waste-free, with only mild overlap between 'sourced fact sheet' and the later sourcing explanation.

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?

The tool is simple (one required id) and an output schema exists, so return values need not be re-explained; the description still adds the sourced/unsourced semantics that make the output interpretable. Only error/failure behavior for an invalid id is unaddressed.

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?

The schema has a single parameter at 100% description coverage and already states the id comes from find_assets results. The description adds no format, validity or fallback guidance for the id beyond what the schema provides, so the baseline of 3 applies.

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?

The description gives a specific verb and resource ('Returns a sourced fact sheet for one UNIALL asset by id') and explicitly enumerates the distinctive payload fields (missing_fields, unsourced_fields). Saying 'one ... asset by id' cleanly separates it from the sibling find_assets list/search tool, and the term 'sourced/citable' distinguishes it from generic summary tools.

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

Usage Guidelines4/5

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

It gives a clear selection cue: 'Useful when you need citable fields for a single asset without inventing data,' which tells the agent to pick this tool for citation-grade single-asset data. It stops short of naming alternatives (find_assets, compare_underlying) or stating when not to use it, so it falls just below the explicit-alternatives bar.

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?