Skip to main content
Glama

solknife_multisig_list

List the Squads multisigs the owner is a member of, found through the owner's recent transactions: address, vault, threshold, and the owner's permissions.

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": {
      "owner": "<owner>"
    },
    "name": "solknife_multisig_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYesA Solana address in base58, 32-44 chars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/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 does disclose the discovery mechanism (derived from the owner's recent transactions) and the four return fields, which is meaningful. However, it never states outright that results may be incomplete for multisigs with no recent activity, nor anything about result limits, ordering, or an empty-result shape.

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?

One front-loaded sentence with the verb and scope first and the return fields in a trailing colon list; no wasted words. Slightly dense, but every clause contributes.

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

Completeness3/5

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

For a one-parameter read tool with no output schema and no annotations, the description does the essentials: what it returns and how it discovers it. It still omits the practical caveat that a sparse transaction history yields incomplete results and says nothing about result size or failure modes for an invalid owner.

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 single `owner` parameter is already documented with format and base58 constraints, so the schema does the heavy lifting. The description adds only the relational meaning (membership is relative to this owner), which is useful but minimal.

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?

The description uses a specific verb and resource ("List the Squads multisigs") and scopes it precisely with "the owner is a member of," plus it enumerates the returned fields (address, vault, threshold, permissions). It does not name a sibling, so it does not explicitly separate itself from solknife_multisig_state, but the "list/many" vs. single-state framing is inferable.

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

Usage Guidelines3/5

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

The phrase "found through the owner's recent transactions" implicitly tells the agent when this tool is applicable (owner-scoped discovery) and hints at its own limitation, but there is no explicit when-not guidance or named alternative such as solknife_multisig_state for a known multisig address.

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