Skip to main content
Glama

account_list_access_keys

Retrieve all access keys associated with a NEAR account. Specify account ID and network to get a complete list of public keys and their permissions.

Instructions

List all access keys for an given account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYes
networkIdNomainnet

Implementation Reference

  • Registration of the 'account_list_access_keys' MCP tool via mcp.tool() in createMcpServer(), defining its name, description, input schema (accountId + networkId), and handler.
    mcp.tool(
      'account_list_access_keys',
      noLeadingWhitespace`
      List all access keys for an given account.`,
      {
        accountId: z.string(),
        networkId: z.enum(['testnet', 'mainnet']).default('mainnet'),
      },
      async (args, _) => {
        const connection = await connect({
          networkId: args.networkId,
          nodeUrl: getEndpointsByNetwork(args.networkId)[0]!,
        });
        const accountResult: Result<Account, Error> = await getAccount(
          args.accountId,
          connection,
        );
        if (!accountResult.ok) {
          return {
            content: [{ type: 'text', text: `Error: ${accountResult.error}` }],
          };
        }
        const accessKeys = await accountResult.value.getAccessKeys();
        return {
          content: [{ type: 'text', text: stringify_bigint(accessKeys) }],
        };
      },
    );
  • Handler function for account_list_access_keys: connects to NEAR, fetches the account, retrieves all access keys via getAccessKeys(), and returns them as a JSON string.
      async (args, _) => {
        const connection = await connect({
          networkId: args.networkId,
          nodeUrl: getEndpointsByNetwork(args.networkId)[0]!,
        });
        const accountResult: Result<Account, Error> = await getAccount(
          args.accountId,
          connection,
        );
        if (!accountResult.ok) {
          return {
            content: [{ type: 'text', text: `Error: ${accountResult.error}` }],
          };
        }
        const accessKeys = await accountResult.value.getAccessKeys();
        return {
          content: [{ type: 'text', text: stringify_bigint(accessKeys) }],
        };
      },
    );
  • Input schema for the tool: accountId (string, required) and networkId (enum 'testnet'|'mainnet', defaults to 'mainnet').
    {
      accountId: z.string(),
      networkId: z.enum(['testnet', 'mainnet']).default('mainnet'),
    },
  • Helper function getAccount used by the handler to fetch a NEAR account by ID, verifying its existence via getAccountBalance().
    const getAccount = async (
      accountId: string,
      connection: Near,
    ): Promise<Result<Account, Error>> => {
      try {
        const account = await connection.account(accountId);
        await account.getAccountBalance();
        return { ok: true, value: account };
      } catch (e) {
        return {
          ok: false,
          error: new Error(
            `Cannot find account by account id ${accountId}: ${e as string}`,
          ),
        };
      }
    };
Behavior2/5

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

No annotations are given. The description implies a read-only operation via 'list,' but lacks explicit statements about side effects, authentication needs, rate limits, or error handling. This is insufficient given the absence of annotations.

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?

The description is a single, clear sentence with no unnecessary words. However, it is almost too concise, lacking details that could improve completeness without sacrificing brevity.

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

Completeness2/5

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

Given no output schema and no annotations, the description leaves out important context: what the returned list contains, pagination, errors, or prerequisites. It is incomplete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description adds minimal value. It implies accountId is the account but does not explain networkId or its enum values, nor any format or constraints. The schema details are not supplemented.

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 clearly states the action 'list' and the resource 'access keys for an given account,' effectively distinguishing it from siblings like account_add_access_key and account_delete_access_keys.

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?

No guidance is provided on when to use this tool versus alternatives such as account_add_access_key or account_delete_access_keys. There are no prerequisites, exclusions, or context for selection.

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/nearai/near-mcp'

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