AI SENSE Free Public Tools

Read temporary data

read_temporary_data

Read-onlyIdempotent

Fetch back a JSON value that store_temporary_data saved earlier, in this session or in another one. Returns the value exactly as it was stored. Fails if the id is unknown or if the 24 hour lifetime has already passed, so treat a failure as expired or never written rather than as a temporary fault worth retrying. sha256_hash is the digest of the stored bytes and bytes their length, the same values store_temporary_data reported. A value stored with max_downloads answers downloads_left, how many reads remain, and is gone once they are taken. No API key, no account and no sign up.

Input Schema

Name	Required	Description	Default
`storage_id`	Yes	The UUID that store_temporary_data returned.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026
- addedOutput schema / properties / downloads_left
```
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",
-  "data",
-  "expire_timestamp"
-]New value: +[
+  "storage_id",
+  "data",
+  "sha256_hash",
+  "bytes",
+  "expire_timestamp"
+]

Changed1 schema field changedAug 20, 2026
- addedInput schema / properties / storage_id / description
```
Added value: +"The UUID that store_temporary_data returned."
```
First observedAug 17, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the 24-hour lifetime, the meaning of failure, the returned digest and byte length, and the max_downloads consumption model (downloads_left, value gone once reads are taken). It also notes no API key or account is required, which matters for agent planning. This is exactly the kind of behavior an agent cannot infer from the annotations.

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 its return semantics are front-loaded, and every sentence carries operational information. It is somewhat run-on and the closing 'No API key, no account and no sign up' is marketing-flavored, but it still conveys a real constraint on usage.

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 read tool with an output schema, the description covers lifetime, failure interpretation, return fields, and download-limited values — everything an agent needs to call it and react to results correctly. Nothing material is left unspecified.

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% and the single parameter is already documented as a UUID from store_temporary_data, so the schema does the heavy lifting. The description adds the consequence of using an id with max_downloads (reads deplete the value) and ties the id's provenance back to the store call, which is meaning beyond the schema.

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 ('Fetch back a JSON value that store_temporary_data saved earlier') and names the paired write tool, so an agent can immediately tell this is the read side of a store/read pair. It also scopes the retrieval to 'in this session or in another one', clarifying cross-session reach.

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?

Usage is clear from context: call it with an id returned by store_temporary_data. It goes further than most by giving a decision rule for failures ('treat a failure as expired or never written rather than as a temporary fault worth retrying'), which directly shapes agent retry behavior. It does not, however, explicitly contrast with a sibling such as read_stored_file, leaving that boundary to inference.

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.