Skip to main content
Glama
lordbasilaiassistant-sudo

base-gasless-deploy-mcp

list_deployed_tokens

Retrieve all ERC-20 tokens deployed by a specific address during the current gasless deployment session on Base network.

Instructions

List tokens deployed by an address in the current session. Tracks all deployments made through this MCP server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deployer_addressYesDeployer wallet address to filter by

Implementation Reference

  • The handler implementation for the list_deployed_tokens tool, which filters a deployments array by deployer or owner address and returns token details.
    async ({ deployer_address }) => {
      try {
        const filtered = deployments.filter(
          (d) =>
            d.deployer.toLowerCase() === deployer_address.toLowerCase() ||
            d.owner.toLowerCase() === deployer_address.toLowerCase()
        );
    
        const tokens = filtered.map((d) => ({
          token_address: d.tokenAddress,
          name: d.name,
          symbol: d.symbol,
          total_supply: d.totalSupply,
          owner: d.owner,
          gasless: d.usedPaymaster,
          tx_hash: d.txHash,
          block_number: d.blockNumber,
          deployed_at: new Date(d.timestamp * 1000).toISOString(),
          explorer: `https://basescan.org/token/${d.tokenAddress}`,
        }));
    
        return mcpResult({
          deployer: deployer_address,
          total: tokens.length,
  • src/index.ts:335-340 (registration)
    Registration and schema definition for the list_deployed_tokens tool in src/index.ts.
    server.tool(
      "list_deployed_tokens",
      "List tokens deployed by an address in the current session. Tracks all deployments made through this MCP server.",
      {
        deployer_address: z.string().describe("Deployer wallet address to filter by"),
      },
Behavior2/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 states the tool lists tokens and tracks deployments, but doesn't disclose critical behaviors such as whether this is a read-only operation, potential rate limits, session-specific constraints, or what the output format looks like (e.g., list structure, pagination). This leaves significant gaps for an agent to understand how to handle results.

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 concise with two sentences that efficiently convey the core purpose and scope. It's front-loaded with the main action and avoids unnecessary details. However, it could be slightly more structured by explicitly separating purpose from behavioral context.

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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., token identifiers, deployment timestamps), session behavior implications, or error conditions. For a tool with one parameter but no structured output guidance, this leaves the agent under-informed about how to interpret results.

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?

Schema description coverage is 100%, with the single parameter 'deployer_address' well-documented in the schema as 'Deployer wallet address to filter by'. The description adds no additional parameter semantics beyond what the schema provides, such as address format examples or filtering nuances. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 clearly states the action ('List tokens deployed') and resource ('by an address'), specifying the scope ('in the current session'). It distinguishes from siblings like 'get_token_info' by focusing on deployment tracking rather than general token information. However, it doesn't explicitly differentiate from all siblings (e.g., 'transfer_tokens' is clearly different, but the distinction could be more explicit).

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 when tracking deployments made through the MCP server, but doesn't provide explicit guidance on when to use this tool versus alternatives like 'get_token_info' for general token details. It mentions the context ('current session') but lacks clear when-not-to-use scenarios or prerequisites beyond the required address 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/lordbasilaiassistant-sudo/base-gasless-deploy-mcp'

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