Skip to main content
Glama
Sign In

Roar AI

by com.roar-ai
OverviewDiscussionsAdmin

An app's file storage

get_app_storage
Read-onlyIdempotent

Whether this app has file storage (an S3-compatible bucket for uploads) and its state: none, creating, ready, error or suspended. When ready, envVars lists the environment variables the app reads — S3_ENDPOINT, S3_BUCKET, S3_REGION, S3_ACCESS_KEY_ID, S3_SECRET_ACCESS_KEY, and the AWS_* aliases an AWS SDK picks up by itself. Values are never returned. Files are private: share one with a presigned URL generated in the app, not by proxying it through the app (that is billed as traffic). Setting an ACL such as public-read has NO effect; public files are a console setting. S3_PUBLIC_URL is present only while the app's files are public.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "appId": "<appId>"
    },
    "name": "get_app_storage"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesThe app id returned by deploy_app or list_apps

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / appId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  2. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Even though annotations already mark it read-only and non-destructive, the description adds substantial context: the complete state enum, which env vars are returned, that values are never returned, the private-file and presigned-URL constraint, ACL behavior, and when `S3_PUBLIC_URL` appears. These are exactly the behavioral details an agent needs beyond the safety annotations.

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?

The first sentence front-loads the purpose and state enum, and subsequent sentences contain relevant operational caveats rather than filler. It is slightly dense and includes storage-usage guidance that is useful but not strictly needed just to invoke the tool.

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

Completeness5/5

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

For a simple one-parameter, read-only tool with no output schema, the description explains the returnable information well: storage state, `envVars` presence when ready, and `S3_PUBLIC_URL` only for public files. Combined with complete parameter and annotation coverage, nothing critical is missing for correct invocation.

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 has 100% description coverage for the single `appId` parameter, so the baseline is 3. The description refers only to “this app” and adds no extra syntax or lookup guidance beyond the schema's `appId` description.

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 that this retrieves an app's file-storage status and enumerates the possible states, so the resource and operation are specific. It does not explicitly distinguish itself from the sibling `add_app_storage`, which is the main sibling an agent might confuse it with.

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?

It explains storage semantics and security behavior, but it does not say when to call this tool rather than `add_app_storage`, `get_app_database`, or other inspection tools. The agent must infer that this is the read-side counterpart to storage creation.

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

All Roar AI toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources