Skip to main content
Glama

listPrompts

Retrieve all available prompts from the MCP Ethers Wallet server to access Ethereum network interactions, wallet management, blockchain queries, and smart contract operations.

Instructions

List all available prompts in the system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that executes the listPrompts tool logic, returning a hardcoded list of available prompts in JSON format.
    async () => {
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            prompts: [
              {
                name: "resolveEnsAcrossNetworks",
                description: "A prompt that guides resolving ENS names on Ethereum mainnet and performing operations with the resolved address on other networks.",
                arguments: [
                  {
                    name: "ensName",
                    description: "The ENS name to resolve (e.g., 'vitalik.eth')",
                    required: true
                  },
                  {
                    name: "targetNetwork",
                    description: "The target network to perform operations on (e.g., 'MEGA Testnet', 'Optimism')",
                    required: true
                  },
                  {
                    name: "operation",
                    description: "The operation to perform: 'balance' for ETH balance, 'txCount' for transaction count, 'code' for contract code",
                    required: true
                  }
                ]
              }
            ]
          }, null, 2)
        }]
      };
    }
  • Registers the listPrompts tool with the MCP server, specifying name, description, empty input schema, and handler function.
      "listPrompts",
      "List all available prompts in the system",
      {},
      async () => {
        return {
          content: [{
            type: "text",
            text: JSON.stringify({
              prompts: [
                {
                  name: "resolveEnsAcrossNetworks",
                  description: "A prompt that guides resolving ENS names on Ethereum mainnet and performing operations with the resolved address on other networks.",
                  arguments: [
                    {
                      name: "ensName",
                      description: "The ENS name to resolve (e.g., 'vitalik.eth')",
                      required: true
                    },
                    {
                      name: "targetNetwork",
                      description: "The target network to perform operations on (e.g., 'MEGA Testnet', 'Optimism')",
                      required: true
                    },
                    {
                      name: "operation",
                      description: "The operation to perform: 'balance' for ETH balance, 'txCount' for transaction count, 'code' for contract code",
                      required: true
                    }
                  ]
                }
              ]
            }, null, 2)
          }]
        };
      }
    );
  • Calls registerPromptTools within the registerAllTools function to include prompt tools in the overall toolset.
    registerPromptTools(server);
  • src/mcpServer.ts:51-51 (registration)
    Top-level call to registerAllTools during MCP server initialization, which indirectly registers the listPrompts tool.
    registerAllTools(server, ethersService);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it's a list operation, implying read-only behavior, but doesn't disclose details like pagination, rate limits, authentication needs, or return format. This is a significant gap for a tool with no annotation coverage.

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?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 annotations, no output schema, and the tool's simplicity (0 params), the description is minimal. It covers the basic purpose but lacks behavioral context (e.g., what 'prompts' are, how results are returned), making it incomplete for effective agent use.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description doesn't add param details, but this is acceptable given the lack of parameters, aligning with the baseline for 0 params.

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 'List all available prompts in the system' clearly states the verb ('List') and resource ('prompts'), with 'all available' specifying scope. However, it doesn't differentiate from sibling tools, which are unrelated blockchain/transaction tools, so no explicit distinction is needed but could be implied.

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. The description lacks context about prerequisites, timing, or exclusions, such as whether it requires authentication or if there are filtering options elsewhere.

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/crazyrabbitLTC/mcp-ethers-server'

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