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.

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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`bytes`	Yes
`read_url`	Yes
`storage_id`	Yes
`sha256_hash`	Yes
`expire_timestamp`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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.4/5.0

Behavior5/5

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

With no informative annotations (all hints false), the description carries the full burden and does so thoroughly: no auth required, public URL, 24-hour TTL, warning against storing secrets, and receipt verification via sha256_hash and byte length. It also explains the REST storage_url and ETag behavior, adding genuine behavioral detail.

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 description is dense but well-organized: purpose, use case, authentication caveat, TTL, retrieval, and verification details all earn their place. It is longer than minimal, but the extra sentences provide high-value operational behavior rather than 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?

For a one-parameter tool with an output schema present, the description is exceptionally complete. It covers when to use it, how to read it back, security limitations, expiration, and integrity verification, leaving an agent well equipped to call it correctly.

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?

Schema coverage is 100% and the schema already fully documents the single data parameter, including that it accepts any JSON type. The description adds a no-secrets reminder but no additional parameter syntax or format details, so the baseline 3 applies.

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 description states a specific verb and resource: 'Put any JSON value somewhere another process can fetch it' and clearly identifies the returned storage_id and public read_url. It is easily distinguished from the sibling read_temporary_data, which retrieves the value.

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?

The description gives explicit use contexts: handing results to another agent, script, webhook receiver, or later run when no shared filesystem or database exists. It also points to read_temporary_data for retrieval, though it does not explicitly list when not to use this tool versus queue/inbox/lease siblings.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.