Skip to main content
Glama
Sign In

AI SENSE Free Public Tools

by com.aisenseapi
OverviewDiscussionsAdmin

Store a file

store_file

Store a file given as base64 for 24 hours, at a link that anyone who has it can open. Answers storage_id and storage_url. Use it to hand a file to another tool, such as an image to process_image or read_qr_code. Never store secrets or personal data. max_downloads, 1 to 100, removes the file after that many fetches; the answer then carries downloads_max and downloads_left, and a spent storage_id answers that the object is gone. No API key, no account and no sign up.

Input Schema

NameRequiredDescriptionDefault
data_base64YesThe file as standard base64, at most about 190 KB of file through MCP. For a larger file, store it with REST POST /services/v1/storage first and pass storage_id.
max_downloadsNoOptional. How many times the file may be fetched before it is removed, 1 to 100. Without it the file lives 24 hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / max_downloads
      Added value: +{
+  "description": "Optional. How many times the file may be fetched before it is removed, 1 to 100. Without it the file lives 24 hours.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the 24-hour TTL, that the URL is bearer-access ('anyone who has it can open'), the no-API-key/no-account posture, and the burn-after-N-fetches semantics including what a spent storage_id returns. These are exactly the operational and safety facts an agent cannot infer from readOnlyHint/destructiveHint.

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?

Front-loads the core action and lifetime, then layers constraints and the max_downloads edge case. Dense but nearly every clause carries new information; the final sentence jumps between return fields and expiry behavior in a way that is slightly harder to parse than it needs to be.

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?

With no output schema, the description still accounts for return values, TTL, access model, authentication requirements, and the exhausted-id case. Combined with a fully documented two-parameter schema, an agent has everything needed to call it correctly and interpret the result.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: what max_downloads actually causes (file removal after that many fetches) and how it surfaces in the response (downloads_max, downloads_left, and an error state for a spent id). Size limits and base64 format are left to the schema, which already documents them thoroughly.

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 ('Store a file given as base64'), plus scope: 24-hour lifetime and a link anyone with it can open. It also names the return values (storage_id, storage_url). It does not explicitly distinguish itself from the sibling store_temporary_data or explain the relationship to read_stored_file, which keeps it below a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit usage context ('hand a file to another tool') with named downstream consumers process_image and read_qr_code, plus a clear prohibition ('Never store secrets or personal data'). What is missing is guidance on when to prefer this over the sibling store_temporary_data, or how it pairs with read_stored_file.

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

All AI SENSE Free Public Tools 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