Skip to main content
Glama
Bankless

Bankless Onchain MCP Server

Official
by Bankless

get_proxy

Retrieve the proxy implementation address for a specified contract on a given blockchain network using the Bankless Onchain MCP Server, enabling access to essential contract data.

Instructions

Gets the proxy address for a given network and contract

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contractYesThe contract address to request the proxy implementation contract for
networkYesThe blockchain network (e.g., "ethereum", "base")

Implementation Reference

  • The core handler function that fetches the proxy implementation for a given contract address on a specified network using the Bankless API endpoint /find-proxy.
    export async function getProxy(
        network: string,
        contract: string
    ): Promise<Proxy> {
        const token = process.env.BANKLESS_API_TOKEN;
    
        if (!token) {
            throw new BanklessAuthenticationError('BANKLESS_API_TOKEN environment variable is not set');
        }
    
        const endpoint = `${BASE_URL}/chains/${network}/contract/${contract}/find-proxy`;
    
        try {
            const response = await axios.get(
                endpoint,
                {
                    headers: {
                        'Content-Type': 'application/json',
                        'X-BANKLESS-TOKEN': `${token}`
                    }
                }
            );
    
            return response.data;
        } catch (error) {
            if (axios.isAxiosError(error)) {
                const statusCode = error.response?.status || 'unknown';
                const errorMessage = error.response?.data?.message || error.message;
    
                if (statusCode === 401 || statusCode === 403) {
                    throw new BanklessAuthenticationError(`Authentication Failed: ${errorMessage}`);
                } else if (statusCode === 404) {
                    throw new BanklessResourceNotFoundError(`Not Found: ${errorMessage}`);
                } else if (statusCode === 422) {
                    throw new BanklessValidationError(`Validation Error: ${errorMessage}`, error.response?.data);
                } else if (statusCode === 429) {
                    // Extract reset timestamp or default to 60 seconds from now
                    const resetAt = new Date();
                    resetAt.setSeconds(resetAt.getSeconds() + 60);
                    throw new BanklessRateLimitError(`Rate Limit Exceeded: ${errorMessage}`, resetAt);
                }
    
                throw new Error(`Bankless API Error (${statusCode}): ${errorMessage}`);
            }
            throw new Error(`Failed to get proxy information: ${error instanceof Error ? error.message : String(error)}`);
        }
    }
  • Zod schema defining the input parameters for the get_proxy tool: network and contract address.
    export const GetProxySchema = z.object({
        network: z.string().describe('The blockchain network (e.g., "ethereum", "base")'),
        contract: z.string().describe('The contract address to request the proxy implementation contract for'),
    });
  • src/index.ts:83-86 (registration)
    Tool registration in the MCP server's listTools handler, specifying name, description, and input schema.
        name: "get_proxy",
        description: "Gets the proxy address for a given network and contract",
        inputSchema: zodToJsonSchema(contracts.GetProxySchema),
    },
  • src/index.ts:160-169 (registration)
    Dispatch logic in the MCP server's CallToolRequest handler that validates input with GetProxySchema and invokes the getProxy function.
    case "get_proxy": {
        const args = contracts.GetProxySchema.parse(request.params.arguments);
        const result = await contracts.getProxy(
            args.network,
            args.contract
        );
        return {
            content: [{type: "text", text: JSON.stringify(result, null, 2)}],
        };
    }
  • TypeScript type definition for the output of the getProxy function.
    export type Proxy = {
        implementation: string;
    };
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes a read operation ('Gets'), implying it's non-destructive, but doesn't cover aspects like error handling, rate limits, authentication needs, or response format. This leaves significant gaps for a tool with no annotation support.

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 that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to understand quickly.

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

Completeness3/5

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

Given the tool's moderate complexity (2 required parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on usage context, behavioral traits, and output expectations, which are needed for effective agent operation.

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, clearly documenting both parameters (network and contract). The description adds minimal value beyond the schema by implying the parameters are used to 'request the proxy implementation contract,' but doesn't provide additional syntax, format details, or examples.

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 ('Gets') and the target resource ('proxy address'), specifying it's for a given network and contract. However, it doesn't differentiate this tool from its siblings (e.g., get_abi, get_source), which also retrieve blockchain-related data but for different resources.

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?

The description provides no guidance on when to use this tool versus alternatives like get_abi or get_source, nor does it mention prerequisites or exclusions. It merely states what the tool does without contextual usage information.

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

Related 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/Bankless/onchain-mcp'

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