trustlayer

get_signed_fact

WITHDRAWN (2026-08-09). This tool does not produce or verify a cryptographic signature and returns a non-success withdrawal notice. Do not rely on it for signed evidence.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_signed_fact"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	Token symbol: USDC, RLUSD, EURC, USDT, DAI
`fact_type`	No	Type: price, peg, market_cap, reserve	price

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations provided, the description fully carries the transparency burden. It clearly discloses that the tool does not produce or verify signatures and that it returns a non-success withdrawal notice. The withdrawal date is also given, providing complete transparency about its status.

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?

The description is two sentences with the critical 'WITHDRAWN' flag front-loaded. Every word contributes meaning: the status, the non-functionality, the behavior, and a warning. No fluff or repetition.

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?

For a deprecated tool with no output schema and no annotations, the description gives all essential context: it is withdrawn, does not perform its named function, and returns a non-success notice. An agent immediately knows to avoid invoking it. Nothing further is needed.

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 input schema provides 100% coverage of both parameters (symbol with enum, fact_type with default and description). The tool description adds no parameter-specific semantics, but since the tool is withdrawn and returns a standard notice regardless of arguments, the schema is sufficient. Baseline 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 explicitly states the tool is 'WITHDRAWN' and clarifies that it 'does not produce or verify a cryptographic signature,' directly contradicting the name's implication. It also specifies the actual behavior: 'returns a non-success withdrawal notice.' This clearly distinguishes it from siblings like verify_signature and evidence_anchor.

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

Usage Guidelines5/5

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

The description provides an explicit when-not instruction: 'Do not rely on it for signed evidence.' This unequivocally tells the agent this tool should not be used for its original purpose, which is sufficient guidance for a deprecated tool.

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

All trustlayer 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?