AI SENSE Free Public Tools

Store temporary data

store_temporary_data

Put any JSON value somewhere another process can fetch it, and get back a storage_id plus a public read_url. Use it to hand a result to a different agent, a script, a webhook receiver or a later run, when there is no shared filesystem and no database between you. No API key, no account and no sign up. Anyone holding the URL can read it, so never store secrets, credentials or personal data. The value disappears 24 hours after it is written. Read it back with read_temporary_data, passing the storage_id. The answer also carries sha256_hash, the digest of the stored bytes, and bytes, their length, so a receiver can tell it got what you sent. The same object over REST calls the link storage_url and serves it with that digest as its ETag. max_downloads, 1 to 100, removes the value after that many reads; the answer then carries downloads_max and downloads_left, and a spent storage_id answers that the object is gone.

Input Schema

Name	Required	Description	Default
`data`	Yes	The JSON value to store. Any type: object, array, string, number, boolean or null. Readable by anyone with the URL, so no secrets.
`max_downloads`	No	Optional. How many times the value may be read before it is removed, 1 to 100. Without it the value lives 24 hours.

Output Schema

Name	Required	Description	Default
`bytes`	Yes
`read_url`	Yes
`storage_id`	Yes
`sha256_hash`	Yes
`downloads_max`	No
`downloads_left`	No
`expire_timestamp`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 6, 2026

addedInput schema / properties / max_downloads

Added value: +{
+  "description": "Optional. How many times the value may be read before it is removed, 1 to 100. Without it the value lives 24 hours.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / downloads_left
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / downloads_max
```
Added value: +{
+  "type": "integer"
+}
```

Changed3 schema fields changedSep 19, 2026

addedOutput schema / properties / bytes
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / sha256_hash
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "storage_id",
-  "read_url",
-  "expire_timestamp"
-]New value: +[
+  "storage_id",
+  "read_url",
+  "sha256_hash",
+  "bytes",
+  "expire_timestamp"
+]

Changed1 schema field changedAug 20, 2026

changedInput schema / properties / data / description

Previous value: -"Any JSON value to store."New value: +"The JSON value to store. Any type: object, array, string, number, boolean or null. Readable by anyone with the URL, so no secrets."

First observedAug 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations: no API key or account needed, public readability of the URL, a 24-hour TTL, max_downloads removal semantics, spent-id behavior, and the sha256_hash/bytes returned for integrity checking. These are exactly the operational facts an agent needs before writing data to a publicly readable location.

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 return values in the first sentence, then layers constraints and lifecycle details. It is dense with useful facts, though the REST-specific aside about storage_url and ETag is marginal overhead for an MCP caller.

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 two-parameter write tool with annotations covering safety, this covers lifecycle, access model, rate-free access, integrity metadata and read-back routing. Even though an output schema exists and return values needn't be explained, the added explanation of hash/bytes/counter fields makes the tool safe to call without inspecting the schema.

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 already 3, and the description adds real meaning: max_downloads removes the value after that many reads and the response then carries downloads_max/downloads_left, while omitting it means the 24-hour default. It restates the 'any JSON type' and no-secrets constraint already in the schema, which is the only redundancy.

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?

Opens with a concrete verb and resource: put a JSON value somewhere another process can fetch, returning storage_id and read_url. It is clearly separable from store_file (files) and the secret-handling siblings, and it names read_temporary_data as the counterpart.

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

Usage Guidelines5/5

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

States the when: handing a result to another agent, script, webhook receiver or later run, specifically when there is no shared filesystem or database. It also names a when-not ('never store secrets, credentials or personal data') and routes the read path to read_temporary_data with the storage_id.

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 tools Inspect

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.