Skip to main content
Glama

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: call it directly.

Input Schema

TableJSON 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.6/5.0
Behavior5/5

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

Annotations only declare the generic write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description goes well beyond that: 24-hour TTL, anyone-with-the-link access, max_downloads causing removal, spent storage_id behavior, and that no API key or account is required. This is exactly the behavioral context annotations cannot carry.

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 what the tool does and what it returns, then layers usage, safety warning, and the max_downloads contract. Dense but each sentence carries information; the closing 'No API key, no account and no sign up' sentence is the least essential, keeping it out of the top band.

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?

There is no output schema, so the description correctly names the return fields (storage_id, storage_url, and downloads_max/downloads_left when capped) and covers lifetime, access model, auth requirements, and removal semantics. An agent has everything needed to call it correctly.

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 baseline is 3. The description still adds value beyond the schema by explaining the consequence of max_downloads (file removed after that many fetches, response then carries downloads_max and downloads_left) and by flagging the 190 KB MCP cap and the REST escape hatch for larger files.

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?

States a specific verb and resource (store a file given as base64), plus the key scoping facts: 24-hour lifetime, public link, and the returned storage_id/storage_url. An agent can distinguish this from read_stored_file, store_temporary_data, and read_temporary_data without opening any schema.

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 a concrete when-to-use: hand a file to another tool such as process_image or read_qr_code, and adds a prohibition (never store secrets or personal data). It does not explicitly contrast with the closest sibling, store_temporary_data, so it stops short of full alternative routing.

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
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources