Skip to main content
Glama

provider_get_storage_at

Query Ethereum or EVM-compatible blockchain storage for a specific address and position. Retrieve stored data using optional block tags for precise blockchain state analysis.

Instructions

Get the storage at a position for an address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe address to get storage from
blockTagNoOptional block tag (latest, pending, etc.)
positionYesThe storage position

Implementation Reference

  • The handler function that executes the logic for 'provider_get_storage_at' by retrieving storage value at a specific position for an address using the ethers provider.
    export const getStorageAtHandler = async (input: any): Promise<ToolResultSchema> => {
      try {
        if (!input.address) {
          return createErrorResponse("Address is required");
        }
    
        if (!input.position) {
          return createErrorResponse("Position is required");
        }
    
        const provider = getProvider();
        const storage = await provider.getStorageAt(input.address, input.position, input.blockTag);
    
        return createSuccessResponse(
        `Storage retrieved successfully
          Address: ${input.address}
          Position: ${input.position}
          Storage: ${storage}
        `);
      } catch (error) {
        return createErrorResponse(`Failed to get storage: ${(error as Error).message}`);
      }
    };
  • The input schema and description definition for the 'provider_get_storage_at' tool.
    {
      name: "provider_get_storage_at",
      description: "Get the storage at a position for an address",
      inputSchema: {
        type: "object",
        properties: {
          address: { type: "string", description: "The address to get storage from" },
          position: { type: "string", description: "The storage position" },
          blockTag: { type: "string", description: "Optional block tag (latest, pending, etc.)" }
        },
        required: ["address", "position"]
      }
    },
  • src/tools.ts:594-594 (registration)
    The registration mapping the tool name 'provider_get_storage_at' to its handler function getStorageAtHandler.
    "provider_get_storage_at": getStorageAtHandler,
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic operation. It doesn't disclose behavioral traits like whether this is a read-only operation (implied by 'get'), potential errors (e.g., invalid address), rate limits, authentication needs, or what the output looks like (e.g., hex data). This leaves significant gaps for an agent.

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 zero waste—it directly states the tool's purpose without redundancy. It's appropriately sized and front-loaded, 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 and no output schema, the description is incomplete for a tool with 3 parameters and blockchain context. It lacks details on return values, error conditions, and operational constraints, which are critical for an agent to use this tool effectively in a provider/wallet environment.

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%, so the schema fully documents parameters (address, blockTag, position). The description adds no additional meaning beyond implying 'storage' relates to 'position' and 'address', which is already clear from parameter names. Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get the storage at a position for an address' clearly states the action (get) and target (storage), but it's vague about what 'storage' means in this context (e.g., blockchain storage slot, data storage). It distinguishes from siblings like provider_get_balance or provider_get_code by specifying storage retrieval, but lacks specificity about the resource type.

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. It doesn't mention prerequisites, such as needing a connected provider or valid blockchain state, nor does it compare to sibling tools like provider_get_logs or wallet_get_balance for related data retrieval.

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/dcSpark/mcp-cryptowallet-evm'

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