Skip to main content
Glama
minhoyoo-iotrust

waiaas

by minhoyoo-iotrust
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

wc_connect

Generate WalletConnect URI to pair external wallets like D'CENT, MetaMask, or Phantom with AI agents for multi-chain crypto operations.

Instructions

Start WalletConnect pairing. Returns a WC URI that the wallet owner can use to connect their external wallet (D'CENT, MetaMask, Phantom, etc). Share the URI with the user -- they can paste it into their wallet app.

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-connect.ts:27-32 (handler)
    The handler function that executes the wc_connect tool by calling the /v1/wallet/wc/pair endpoint via the apiClient.
    async (args) => {
  const body: Record<string, unknown> = {};
  if (args.wallet_id) body.walletId = args.wallet_id;
  const result = await apiClient.post('/v1/wallet/wc/pair', body);
  return toToolResult(result);
},
  • packages/mcp/src/tools/wc-connect.ts:13-34 (registration)
    The registration function for the wc_connect tool in the MCP server.
    export function registerWcConnect(
  server: McpServer,
  apiClient: ApiClient,
  walletContext?: WalletContext,
): void {
  server.tool(
    'wc_connect',
    withWalletPrefix(
      "Start WalletConnect pairing. Returns a WC URI that the wallet owner can use to connect their external wallet (D'CENT, MetaMask, Phantom, etc). Share the URI with the user -- they can paste it into their wallet app.",
      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 body: Record<string, unknown> = {};
      if (args.wallet_id) body.walletId = args.wallet_id;
      const result = await apiClient.post('/v1/wallet/wc/pair', body);
      return toToolResult(result);
    },
  );
}

Tool Definition Quality

A4.2/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 burden of behavioral disclosure. It successfully communicates the return value (WC URI) and the external user flow required to complete the pairing. However, it omits details about session persistence (that a wc_disconnect exists to terminate it), URI expiration, or whether the call blocks until connection completes.

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?

Three sentences with zero waste: sentence 1 states the action, sentence 2 describes the return value and supported wallets, sentence 3 gives the user instruction. Information is front-loaded with the core action 'Start WalletConnect pairing' immediately identifying the tool's function.

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?

Given the absence of an output schema, the description appropriately compensates by explicitly stating the tool returns a 'WC URI' and explaining what to do with it. It adequately covers the single optional parameter and implies the session lifecycle context (via 'pairing'), though mentioning the relationship to wc_disconnect would strengthen completeness.

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 single wallet_id parameter ('Target wallet ID. Required for multi-wallet sessions; auto-resolved when session has a single wallet'). The description adds no supplemental parameter information, meeting the baseline expectation when the schema is already self-documenting.

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 uses the specific verb 'Start' with the resource 'WalletConnect pairing', clearly indicating this initiates a connection flow. It distinguishes itself from siblings wc_disconnect (termination) and wc_status (monitoring) by emphasizing the initiation aspect and return of a connection URI.

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?

The description provides clear workflow guidance: explains that the returned URI must be shared with the user for them to paste into their wallet app (D'CENT, MetaMask, Phantom). It effectively communicates the 'when' (initiating external wallet connections) and 'how', though it lacks explicit exclusionary guidance (e.g., 'do not use if already connected').

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