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

TableJSON 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

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

Behavior5/5

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

Annotations only declare the write/non-idempotent/non-destructive profile; the description goes well beyond them by disclosing no auth or account needed, public URL readability, a 24-hour TTL, the sha256_hash/bytes returned, ETag behavior over REST, max_downloads semantics with downloads_max/downloads_left, and that a spent storage_id reports the object is gone. That is unusually rich behavioral context for a mutation tool.

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 core action and return shape are front-loaded in sentence one, and each subsequent sentence carries distinct information (safety warning, TTL, read-back tool, digest/length, REST naming, max_downloads). It is on the long side and the REST/storage_url aside is arguably secondary, but nothing is pure filler.

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?

An output schema exists, yet the description still supplies the operational facts an agent needs: safety constraint (no secrets), expiry, read-back path, integrity fields, and read-count limits. Nothing material for correct invocation is missing.

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 description coverage is already 100%, so the baseline is 3. The description adds real meaning beyond the schema: that 'data' may be any JSON type including null, and that max_downloads (1-100) removes the value after that many reads and causes downloads_max/downloads_left to appear in the response.

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?

The opening sentence gives a specific verb and resource ('put any JSON value somewhere another process can fetch it') plus the concrete artifacts returned (storage_id, public read_url). It is clearly distinguishable from siblings store_file/read_stored_file (file storage) and read_temporary_data (retrieval).

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?

It states the use case explicitly — handing a result to another agent, script, webhook receiver or later run when there is no shared filesystem or database — and names read_temporary_data as the read-back path. It does not, however, say when to prefer store_file or read_stored_file instead, so sibling exclusion is only partial.

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

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.