Skip to main content
Glama

get_blob_info

Retrieve blob information including size and availability status from the Walrus decentralized storage network using a blob ID.

Instructions

Get information about a blob (size, availability, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blobIdYesThe blob ID to get information about

Implementation Reference

  • MCP tool handler for 'get_blob_info': parses input using schema, calls walrusClient.getBlobInfo, and returns JSON stringified result.
    case 'get_blob_info': {
      const { blobId } = GetBlobInfoSchema.parse(args);
      const result = await walrusClient.getBlobInfo(blobId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Zod schema for validating input arguments to get_blob_info tool (blobId: string).
    const GetBlobInfoSchema = z.object({
      blobId: z.string().describe('The blob ID to get information about'),
    });
  • src/index.ts:116-129 (registration)
    Registration of 'get_blob_info' tool in the ListTools response, including name, description, and input schema.
    {
      name: 'get_blob_info',
      description: 'Get information about a blob (size, availability, etc.)',
      inputSchema: {
        type: 'object',
        properties: {
          blobId: {
            type: 'string',
            description: 'The blob ID to get information about',
          },
        },
        required: ['blobId'],
      },
    },
  • Core implementation of getBlobInfo: performs HEAD request to aggregator to get blob metadata like size, assumes certified if accessible.
    async getBlobInfo(blobId: string): Promise<BlobInfo> {
      try {
        // Try to get blob head information
        const response = await this.httpClient.head(`${this.config.aggregatorUrl}/v1/${blobId}`);
        
        const size = parseInt(response.headers['content-length'] || '0');
        
        return {
          blobId,
          size,
          encodedSize: size, // Approximate, actual encoded size may differ
          storageId: blobId,
          certified: true, // If we can access it, it's certified
        };
      } catch (error) {
        if (axios.isAxiosError(error)) {
          if (error.response?.status === 404) {
            throw new Error(`Blob not found: ${blobId}`);
          }
          throw new Error(`Failed to get blob info: ${error.response?.data?.error || error.message}`);
        }
        throw new Error(`Failed to get blob info: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
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. It states the tool retrieves information, implying a read-only operation, but doesn't disclose behavioral traits such as authentication needs, rate limits, error conditions, or what 'availability' entails. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 front-loads the core purpose ('Get information about a blob') and adds specific details ('size, availability, etc.') without waste. Every word earns its place, making it appropriately sized and well-structured for quick comprehension.

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 low complexity (single parameter, read-only implied), 100% schema coverage, and no output schema, the description is minimally adequate. It covers the basic purpose but lacks context on behavioral aspects (e.g., permissions, errors) and doesn't explain return values. Without annotations, it should do more to compensate, but the simplicity keeps it from being severely incomplete.

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 schema description coverage is 100%, with the single parameter 'blobId' documented in the schema. The description adds no additional meaning about the parameter beyond what the schema provides (e.g., format examples or constraints). With high schema coverage, the baseline score of 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.

Purpose4/5

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

The description clearly states the verb ('Get') and resource ('blob'), specifying the type of information retrieved ('size, availability, etc.'). It distinguishes from siblings like 'get_blob' (likely retrieves content) and 'list_blobs' (lists multiple), but doesn't explicitly contrast them. The purpose is specific but lacks explicit sibling differentiation.

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_blob' or 'list_blobs'. It implies usage for retrieving metadata about a specific blob, but offers no explicit context, exclusions, or prerequisites. This leaves the agent to infer usage from the tool name and description alone.

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/Motion-Labs-Sui/walrus-mcp'

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