Skip to main content
Glama

rwa_asset_due_diligence

Read-onlyIdempotent

Fail-closed issuer, contract, jurisdiction, custody and documentation coverage with independently fetched evidence; 0.019 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": {
        "name": "Tokenized Treasury",
        "issuer": "Issuer",
        "network": "eip155:8453",
        "contract": "0x...",
        "custodian": "Example Custodian",
        "jurisdiction": "US",
        "documentation": "https://issuer.example/disclosures"
      },
      "source_urls": [
        "https://issuer.example/disclosures"
      ]
    },
    "name": "rwa_asset_due_diligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYes
source_urlsNo
declared_factsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "asset": {
      +      "contract": "0x...",
      +      "custodian": "Example Custodian",
      +      "documentation": "https://issuer.example/disclosures",
      +      "issuer": "Issuer",
      +      "jurisdiction": "US",
      +      "name": "Tokenized Treasury",
      +      "network": "eip155:8453"
      +    },
      +    "source_urls": [
      +      "https://issuer.example/disclosures"
      +    ]
      +  }
      +]
  2. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context – 'fail-closed' error semantics, 'independently fetched evidence' (consistent with openWorldHint), and a cost of 0.019 USDC – but says nothing about what a failure returns or what the report contains.

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?

A single front-loaded sentence with no filler, and the cost is appended efficiently. It is terse to the point of being cryptic, but nothing is wasted.

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?

For a three-parameter tool with nested objects, 0% schema coverage and no output schema, the description should explain return shape (pass/fail vs coverage report), the distinction between `asset`, `source_urls` and `declared_facts`, and failure behavior. It leaves all of these 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?

Schema description coverage is 0% with three parameters, so the description carries real burden. It partially compensates by enumerating issuer, contract, jurisdiction, custody and documentation (fields expected inside the nested `asset` object) and by implying external fetching for `source_urls`, but `declared_facts` and the array/nesting semantics are never explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (asset due diligence) and enumerates the dimensions checked – issuer, contract, jurisdiction, custody, documentation – so an agent can infer it is a multi-dimensional coverage check. However, 'Fail-closed ... coverage' is dense jargon with no clear verb, and it never distinguishes itself from siblings like rwa_compliance or rwa_sanctions_screening_evidence.

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?

There is no statement of when to use this tool versus alternatives such as rwa_compliance or rwa_sanctions_screening_evidence, nor any prerequisites. The only contextual hint is the price '0.019 USDC', which signals a paid call but does not guide selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources