ChainRay

Multi-Sig Analysis

util.multi_sig

Read-onlyIdempotent

Analyze a Gnosis Safe multi-sig wallet. Returns owners, threshold, nonce, modules, and security assessment.

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": {
      "address": "<address>"
    },
    "name": "util.multi_sig"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No	EVM chain only. Supported chains: base, ethereum, arbitrum, optimism, polygon, bsc, avalanche, zksync, linea, scroll, blast, mantle, gnosis, polygon-zkevm, mode, sei, celo, manta, taiko, fantom, cronos, opbnb, zora, worldchain, metis, fraxtal, kava, zetachain, filecoin, core-dao, aurora, moonbeam, klaytn, bob, canto, monad, tempo, megaeth, arc, plasma, katana, robinhood, pharos, hyperevm.	base
`address`	Yes	Gnosis Safe contract address

Output Schema

Name	Required	Description
`data`	No
`chain`	Yes	Blockchain queried
`owners`	No
`address`	Yes	Address
`threshold`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 3, 2026
RemovedOct 2, 2026
First observedOct 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety behavior is fully covered without the description. The description adds only a list of returned fields, which is largely redundant with the existing output schema, and says nothing about failure modes (non-Safe address), rate limits, or chain-dependent behavior. Some added value, but thin against annotation coverage.

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?

Two short sentences with zero filler: the action and target come first, the output summary second. Nothing is repeated from the title, and every clause earns its place.

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?

For a read-only, two-parameter tool with full schema coverage, complete annotations, and an output schema, the description is nearly sufficient. The only shortfall is that it does not mention what happens with a non-Safe or unsupported-chain address, leaving the error surface implicit.

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 100% and the chain enum with 44 values plus the 'Gnosis Safe contract address' description already carry the parameter semantics. The description adds no format, validation, or default guidance beyond what the schema states, so the baseline 3 for high coverage 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 ('Analyze') and a precisely scoped resource ('Gnosis Safe multi-sig wallet'), which no sibling tool covers. The enumeration of returned fields (owners, threshold, nonce, modules, security assessment) makes the analysis output concrete and separates it from generic tools like wallet.profile or security.contract.scan.

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?

The description never says when to choose this over alternatives (e.g. security.contract.scan or wallet.report for a Safe address) and states no prerequisites. It implies its domain via the object of the verb, but leaves all routing decisions to inference, matching the mid-tier calibration of 'no when-to-use, no prerequisites'.

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

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