Signo

Signo: wallet insights report

wallet_insights_report

Read-only

Analyze any public onchain wallet and return its Signo Score plus prioritized findings. Covers yield left on the table, leverage safety, LP health, idle capital, dust and unclaimed rewards. Read-only: it inspects public chain data and never moves funds, needs no keys, and requires no connected session — so it works on any address you can name, not just one the caller controls. Returns signoScore (0-100, the Signo Score: how well the wallet's capital is managed, from idle cash, yield against the cash benchmark, unclaimed rewards, the leverage guard and dust; it is not a safety or liquidation-risk score). This public tool cannot read the owner's private Agents, so watch coverage is not_applicable with 'Agent coverage isn't shown here' and signoScore omits that category; the signed-in owner's app score can differ. riskTolerance, walletAge, holdings (every chain's tokens, DeFi positions and loans with USD values, largest first, so you can structure your own view), and a categories array where each entry carries state, headline, detail and a suggested next step. Findings that call for an agent carry agentSuggestion, and the report carries suggestedAgents plus draftWith: exact request and autonomy arguments for the sibling signo_draft_agent tool on this host, so you can draft the agent for the wallet owner to activate. Free.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`address`	Yes	The wallet to analyze — an EVM address (0x + 40 hex) or a Solana base58 address.
`narrative`	No	Include a written plain-English summary alongside the structured findings. Slower; defaults to false.

Output Schema

TableJSON Schema

Name	Required	Description
`chain`	No
`address`	No
`holdings`	No	Every chain's tokens, DeFi positions and loans with USD values.
`draftWith`	No	Exact arguments for signo_draft_agent on this host.
`narrative`	No
`walletAge`	No
`categories`	Yes	Findings: state, headline, detail, next step, and agentSuggestion where an agent fits.
`signoScore`	Yes	0-100: how well the wallet's capital is managed; null when nothing could be read.
`generatedAt`	No
`zeroActivity`	No
`riskTolerance`	No
`netPortfolioUsd`	No
`suggestedAgents`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "address": {
+      "type": "string"
+    },
+    "categories": {
+      "description": "Findings: state, headline, detail, next step, and agentSuggestion where an agent fits.",
+      "items": {},
+      "type": "array"
+    },
+    "chain": {
+      "type": "string"
+    },
+    "draftWith": {
+      "description": "Exact arguments for signo_draft_agent on this host."
+    },
+    "generatedAt": {
+      "type": "number"
+    },
+    "holdings": {
+      "description": "Every chain's tokens, DeFi positions and loans with USD values."
+    },
+    "narrative": {},
+    "netPortfolioUsd": {
+      "type": "number"
+    },
+    "riskTolerance": {},
+    "signoScore": {
+      "description": "0-100: how well the wallet's capital is managed; null when nothing could be read.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "suggestedAgents": {
+      "items": {},
+      "type": "array"
+    },
+    "walletAge": {},
+    "zeroActivity": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "signoScore",
+    "categories"
+  ],
+  "type": "object"
+}

First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial context beyond them — never moves funds, no keys, no session required, free, public-only scope, and the explicit caveat that watch coverage is not_applicable and the owner's app score can differ. It also discloses a limitation of the score itself (not a safety or liquidation-risk score).

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?

Purpose is front-loaded and the prose is dense with useful caveats, but it is a single very long paragraph that spends considerable space describing return values even though an output schema exists. It mostly earns its place but is longer than strictly necessary.

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?

Given a read-only, two-param tool with an output schema, the description supplies everything an agent needs: purpose, safety profile, scope limits, score semantics, and the handoff to signo_draft_agent. Return-shape detail is a bonus rather than a gap.

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 coverage is 100%, so both parameters are already documented in the schema (address formats, narrative slowness/default). The description reinforces 'any address you can name' but adds no syntax or format detail beyond what the schema provides, so the 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?

States a specific verb and resource ('Analyze any public onchain wallet and return its Signo Score plus prioritized findings') and enumerates the analysis categories. It clearly differentiates itself from siblings by positioning signo_draft_agent as the downstream consumer, so an agent can place it in the workflow without opening the schema.

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?

Explains the key selection context — read-only, no keys, no session, works on any address you can name 'not just one the caller controls' — and points to signo_draft_agent for drafting. It lacks an explicit when-not-to-use or a contrast against the owner-app score path beyond noting they can differ.

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

All Signo 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.