Skip to main content
Glama
minhoyoo-iotrust

waiaas

by minhoyoo-iotrust
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

wc_status

Check active WalletConnect session status to verify wallet connections, view peer wallet details, chain information, and session expiry.

Instructions

Get WalletConnect session status. Returns session info (peer wallet, chain, expiry) or error if no active session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallet_idNoTarget wallet ID. Required for multi-wallet sessions; auto-resolved when session has a single wallet.

Implementation Reference

  • packages/mcp/src/tools/wc-status.ts:27-33 (handler)
    The handler function that calls the /v1/wallet/wc/session API endpoint.
    async (args) => {
  const params = new URLSearchParams();
  if (args.wallet_id) params.set('walletId', args.wallet_id);
  const qs = params.toString();
  const result = await apiClient.get('/v1/wallet/wc/session' + (qs ? '?' + qs : ''));
  return toToolResult(result);
},
  • packages/mcp/src/tools/wc-status.ts:13-35 (registration)
    The registration function for the wc_status MCP tool.
    export function registerWcStatus(
  server: McpServer,
  apiClient: ApiClient,
  walletContext?: WalletContext,
): void {
  server.tool(
    'wc_status',
    withWalletPrefix(
      'Get WalletConnect session status. Returns session info (peer wallet, chain, expiry) or error if no active session.',
      walletContext?.walletName,
    ),
    {
      wallet_id: z.string().optional().describe('Target wallet ID. Required for multi-wallet sessions; auto-resolved when session has a single wallet.'),
    },
    async (args) => {
      const params = new URLSearchParams();
      if (args.wallet_id) params.set('walletId', args.wallet_id);
      const qs = params.toString();
      const result = await apiClient.get('/v1/wallet/wc/session' + (qs ? '?' + qs : ''));
      return toToolResult(result);
    },
  );
}

Tool Definition Quality

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the full disclosure burden. It compensates effectively by detailing the return structure (peer wallet, chain, expiry) and error condition (no active session), giving the agent clear expectations about response shape and failure modes. It does not explicitly confirm read-only safety, though 'Get' implies this.

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 sentences with zero waste: the first front-loads the core purpose, the second explains return values and error handling. Every clause earns its place; there is no redundant elaboration or marketing language.

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 single-parameter tool without output schema or annotations, the description is complete. It compensates for the missing output schema by enumerating returned fields (peer wallet, chain, expiry) and covers the conditional requirement logic (multi-wallet vs single-wallet) within the schema description.

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 has 100% description coverage for the wallet_id parameter, documenting the auto-resolution behavior for single-wallet sessions. The description does not add additional parameter semantics beyond the schema, meeting the baseline score of 3 for high-coverage schemas.

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 opens with the specific verb 'Get' and明确的资源 'WalletConnect session status', clearly distinguishing it from sibling tools like wc_connect (initiates), wc_disconnect (terminates), and list_sessions (enumerates). It precisely scopes the tool to checking the status of an existing session rather than performing lifecycle operations.

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 description implies usage through the error condition 'or error if no active session', hinting this should be used to verify session existence. However, it lacks explicit guidance on when to use this versus list_sessions or whether it should be called before wc_disconnect, leaving usage patterns implied rather than stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/minhoyoo-iotrust/WAIaaS'

If you have feedback or need assistance with the MCP directory API, please join our Discord server