PHION RWA

rwa_corporate_actions

Detect and sign material RWA changes in NAV, income, maturity, redemption or freeze state; 0.012 USDC.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asset": {
        "contract": "0x..."
      },
      "source_urls": [
        "https://issuer.example/notices"
      ],
      "current_state": {
        "nav": "1.01",
        "frozen": false
      },
      "previous_state": {
        "nav": "1.00",
        "frozen": false
      }
    },
    "name": "rwa_corporate_actions"
  }
}

Input Schema

Name	Required	Description	Default
`asset`	Yes
`source_urls`	No
`current_state`	Yes
`previous_state`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

addedInput schema / examples

Added value: +[
+  {
+    "asset": {
+      "contract": "0x..."
+    },
+    "current_state": {
+      "frozen": false,
+      "nav": "1.01"
+    },
+    "previous_state": {
+      "frozen": false,
+      "nav": "1.00"
+    },
+    "source_urls": [
+      "https://issuer.example/notices"
+    ]
+  }
+]

First observedSep 24, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It mentions signing and a cost (0.012 USDC), but does not disclose what signing entails (on-chain transaction?), whether it is destructive or irreversible, or what credentials are needed. The materiality threshold and freeze detection logic are also unspecified.

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?

A single, information-dense sentence that front-loads the action and key fields. No extraneous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given four parameters with 0% schema coverage, nested objects, and no annotations or output schema, the description is insufficient. It lacks critical details on parameter formats, signing behavior, and materiality criteria needed to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description provides no parameter details. It doesn't explain the expected structure of asset, current_state, previous_state, or source_urls, leaving the agent to guess the nested object schemas and required fields beyond the example.

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?

States a specific verb (detect and sign) and resource (material RWA changes) with the exact fields monitored (NAV, income, maturity, redemption, freeze state). It is distinguishable from siblings like rwa_nav_reserve, though the signing aspect slightly overlaps with verify.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs alternatives. The description only states what it does and a price, without context on prerequisites, when a change is considered material, or how it differs from rwa_nav_reserve or verify.

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

All PHION RWA 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?