Skip to main content
Glama

get_provider_status

Check Smart Account provider details including name, supported chains, and gas sponsorship status for a specific wallet.

Instructions

Get Smart Account provider status: provider name, supported chains, gas sponsorship (paymaster) status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallet_idYesTarget wallet ID (UUID).

Implementation Reference

  • The handler function for 'get_provider_status' which fetches the wallet data from the API and processes the provider status information for smart accounts.
    async (args) => {
      const result = await apiClient.get<Record<string, unknown>>(
        '/v1/wallets/' + args.wallet_id,
      );
      if (!result.ok) return toToolResult(result);
    
      const wallet = result.data;
      const provider = wallet['provider'] as { name: string; supportedChains: string[]; paymasterEnabled: boolean } | null;
      const accountType = (wallet['accountType'] as string) ?? 'eoa';
    
      if (accountType !== 'smart') {
        return {
          content: [{ type: 'text' as const, text: JSON.stringify({ accountType, provider: null, message: 'This is an EOA wallet. Smart Account provider is only applicable to smart account wallets.' }) }],
        };
      }
    
      if (!provider) {
        return {
          content: [{ type: 'text' as const, text: JSON.stringify({ accountType: 'smart', provider: null, message: 'No provider configured. Use PUT /v1/wallets/:id/provider to set up a provider (pimlico, alchemy, or custom).' }) }],
        };
      }
    
      return {
        content: [{ type: 'text' as const, text: JSON.stringify({
          accountType: 'smart',
          provider: {
            name: provider.name,
            supportedChains: provider.supportedChains,
            paymasterEnabled: provider.paymasterEnabled,
            gasSponsorshipStatus: provider.paymasterEnabled ? 'Gas fees are sponsored by the paymaster on supported chains.' : 'No paymaster configured. Transactions require the wallet to hold native gas tokens.',
          },
        }) }],
      };
    },
  • The registration function that registers the 'get_provider_status' tool with the McpServer.
    export function registerGetProviderStatus(server: McpServer, apiClient: ApiClient, walletContext?: WalletContext): void {
      server.tool(
        'get_provider_status',
        withWalletPrefix('Get Smart Account provider status: provider name, supported chains, gas sponsorship (paymaster) status.', walletContext?.walletName),
        {
          wallet_id: z.string().describe('Target wallet ID (UUID).'),
        },
        async (args) => {
          const result = await apiClient.get<Record<string, unknown>>(
            '/v1/wallets/' + args.wallet_id,
          );
          if (!result.ok) return toToolResult(result);
    
          const wallet = result.data;
          const provider = wallet['provider'] as { name: string; supportedChains: string[]; paymasterEnabled: boolean } | null;
          const accountType = (wallet['accountType'] as string) ?? 'eoa';
    
          if (accountType !== 'smart') {
            return {
              content: [{ type: 'text' as const, text: JSON.stringify({ accountType, provider: null, message: 'This is an EOA wallet. Smart Account provider is only applicable to smart account wallets.' }) }],
            };
          }
    
          if (!provider) {
            return {
              content: [{ type: 'text' as const, text: JSON.stringify({ accountType: 'smart', provider: null, message: 'No provider configured. Use PUT /v1/wallets/:id/provider to set up a provider (pimlico, alchemy, or custom).' }) }],
            };
          }
    
          return {
            content: [{ type: 'text' as const, text: JSON.stringify({
              accountType: 'smart',
              provider: {
                name: provider.name,
                supportedChains: provider.supportedChains,
                paymasterEnabled: provider.paymasterEnabled,
                gasSponsorshipStatus: provider.paymasterEnabled ? 'Gas fees are sponsored by the paymaster on supported chains.' : 'No paymaster configured. Transactions require the wallet to hold native gas tokens.',
              },
            }) }],
          };
        },
      );
    }
Behavior3/5

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

Without annotations, the description carries the burden of disclosing output fields (provider name, chains, paymaster status) but omits operational details like idempotency, caching behavior, or error conditions.

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?

Single sentence efficiently structured as Verb:Resource:Fields with zero redundant words, front-loading the action and specific return values.

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 single parameter and lack of output schema, listing the three specific return fields provides sufficient context for a simple status retrieval tool, though provider context could be explicit.

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?

With 100% input schema coverage, the UUID wallet_id parameter is well-documented in the schema itself; the description adds no parameter semantics but meets the baseline expectation.

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?

Description uses specific verb 'Get' and identifies resource 'Smart Account provider status', listing return fields (provider name, supported chains, paymaster status) that clearly distinguish it from sibling wallet info tools.

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?

Description only states what the tool retrieves without indicating when to use it versus alternatives like get_wallet_info, or prerequisites for the wallet_id parameter.

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