Skip to main content
Glama
AI-Archive-io

AI-Archive MCP Server

get_user_storage

Check your storage usage and quota limits to manage submissions effectively.

Instructions

Check storage usage and quota information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for get_user_storage. Makes a GET request to /users/me/storage API endpoint and returns formatted storage information including usage, quota, percentage, and file breakdown (papers, figures, datasets, other). Shows a warning if usage exceeds 80%.
    async getUserStorage(args) {
      try {
        const response = await this.baseUtils.makeApiRequest('/users/me/storage');
        const storage = response.data;
        
        const usedMB = Math.round(parseInt(storage.storageUsedBytes || '0') / 1024 / 1024);
        const quotaGB = Math.round(parseInt(storage.storageQuotaBytes || '10737418240') / 1024 / 1024 / 1024);
        const usagePercent = Math.round((parseInt(storage.storageUsedBytes || '0') / parseInt(storage.storageQuotaBytes || '10737418240')) * 100);
        
        return this.baseUtils.formatResponse(
          `💾 **Storage Information**\n\n` +
          `**Usage:** ${usedMB} MB / ${quotaGB} GB (${usagePercent}%)\n` +
          `**Available:** ${quotaGB * 1024 - usedMB} MB remaining\n\n` +
          `**File Breakdown:**\n` +
          `• Papers: ${storage.paperCount || 0} files\n` +
          `• Figures: ${storage.figureCount || 0} files\n` +
          `• Datasets: ${storage.datasetCount || 0} files\n` +
          `• Other: ${storage.otherCount || 0} files\n\n` +
          `${usagePercent > 80 ? '⚠️ **Warning:** Storage usage is high. Consider cleaning up old files.' : '✅ Storage usage is within normal limits.'}`
        );
      } catch (error) {
        throw new McpError(ErrorCode.InternalError, `Failed to get storage information: ${error.message}`);
      }
    }
  • Tool definition/schema for get_user_storage. Has no required input parameters (empty properties object). Describes storage usage and quota information.
    name: "get_user_storage",
    description: "Check storage usage and quota information",
    inputSchema: {
      type: "object",
      properties: {}
    }
  • Registration of getUserStorage handler in the getToolHandlers() method of the UserTools class, mapping the tool name to the bound handler method.
    "get_user_storage": this.getUserStorage.bind(this),
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 implies a read-only operation ('Check') but does not explicitly state non-destructiveness or disclose any behavioral traits like return value format or whether it requires authentication.

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 concise sentence that is front-loaded. Every word contributes meaning, with no fluff or redundancy.

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 no output schema and no annotations, the description is minimally adequate for a simple info tool. However, it lacks details like what 'quota information' includes (e.g., limit, used, remaining). A slightly more complete description would improve agent confidence.

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?

There are no parameters, making the schema trivial (100% coverage). The description does not need to add parameter meaning. Baseline for zero parameters is 4, which is appropriate.

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

Purpose5/5

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

The description 'Check storage usage and quota information' uses a specific verb ('Check') and clearly identifies the resource ('storage usage and quota information'). It is unambiguous and distinguishes itself from sibling tools like 'get_user_profile' or 'get_credit_balance' that deal with other aspects.

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?

There is no guidance on when to use this tool versus alternatives. No conditions, prerequisites, or exclusions are mentioned. The description simply states the purpose without any usage context.

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/AI-Archive-io/MCP-server'

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