Skip to main content
Glama

Enable storage

enable_storage
Idempotent

Enable file storage (S3-compatible). Injects STORAGE_BUCKET, STORAGE_REGION, STORAGE_ACCESS_KEY, STORAGE_SECRET_KEY, STORAGE_PREFIX, STORAGE_PUBLIC_URL; restart the preview afterwards. Keys go under STORAGE_PREFIX; public URL = STORAGE_PUBLIC_URL + '/' + key; no ACLs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "enable_storage"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNoProject id (or use session from use_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare idempotent=true, destructive=false, readOnly=false, so safety basics are covered; the description goes further by naming the injected environment variables, the required preview restart, the key layout under STORAGE_PREFIX, the public URL construction rule, and the absence of ACLs. It stops short of saying what happens to existing objects when storage is re-enabled or disabled later.

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?

Two sentences, front-loaded with the core action, then dense but relevant operational facts. The environment-variable enumeration is long yet functional rather than filler.

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

Completeness4/5

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

For a one-parameter mutation with no output schema and clear annotations, the description covers effects, env vars, restart requirement, key/URL conventions, and ACL policy. Gaps are minor: permissions or cost implications and the fate of pre-existing storage state are unstated.

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?

With a single parameter and 100% schema description coverage, the schema already explains project_id and the session fallback via use_project. The description adds nothing about that parameter, so baseline 3 applies.

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?

States a specific verb and resource ('Enable file storage') plus a qualifying detail ('S3-compatible'), so the agent knows exactly what capability is being turned on. The inverse sibling disable_storage is obvious, but the description never explicitly frames the pairing.

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?

Usage is implied rather than stated: an agent infers this is the tool for adding object storage, and the 'restart the preview afterwards' clause gives a useful workflow constraint. There is no explicit when-to-use/when-not-to-use framing or reference to related tools such as storage_upload or disable_storage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources