Skip to main content
Glama

AI SENSE Free Public Tools

by com.aisenseapi

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. No API key, no account and no sign up: call it directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
storage_idYesThe UUID that store_temporary_data returned.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
storage_idYes
expire_timestampYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / storage_id / description
      Added value: +"The UUID that store_temporary_data returned."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true and idempotentHint=true, but the description adds critical behavioral context: the 24-hour lifetime, failure semantics (expired or never written), and that no authentication is needed. This goes beyond the hints, albeit not significantly; score reflects strong transparency but not perfect depth.

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 concise and front-loaded with the core purpose in the first sentence. Subsequent sentences add essential error handling and authentication context. Every sentence contributes value, though slightly longer than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given there is an output schema, the description need not explain return values, and it doesn't. It covers key context: provenance (previous store call), lifetime (24h), and failure mode. It could mention what the value looks like (but output schema does) and any rate limits, but overall adequate for a simple tool.

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?

The schema fully describes storage_id with a description ('The UUID that store_temporary_data returned.'), so parameter semantics are already covered. The description adds no extra parameter-level detail, but since coverage is 100%, a baseline of 3 is appropriate.

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 clearly states the tool retrieves a JSON value stored by store_temporary_data, specifying the resource (temporary data) and the action (read/fetch). It distinguishes from siblings like read_webhook_capture and read_human_approval by focusing on temporary data and referencing its companion store tool.

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?

The description explicitly explains when to use the tool: to retrieve previously stored temporary data, and when not to retry on failure (since failures indicate expired or never-written IDs). This guides the agent to avoid unnecessary retries, which is crucial behavioral guidance, even though it does not name alternatives directly.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool belongs to a clearly separated resource family: leases, heartbeats, human approvals, webhook captures, temporary data, and small utilities. Even similar-sounding tools like create_agent_wake and create_heartbeat are differentiated by their descriptions: durable task completion versus deadline monitoring.

Naming Consistency5/5

Tool names consistently use a snake_case verb_noun pattern, such as acquire_lease, create_heartbeat, read_webhook_capture, and store_temporary_data. Paired operations read naturally, with only a minor and acceptable variation between get_current_time and the read_* tools.

Tool Count4/5

At 18 tools, this is slightly above the ideal 3-15 range, but the server intentionally bundles several independent public utilities rather than one narrow domain. Each tool has a distinct purpose, so the count feels full but not bloated.

Completeness4/5

Core workflows are well covered: leases support acquire, renew, release, and complete; heartbeats support create, ping, and read; captures, approvals, and temporary data have create/read or store/read pairs. There are no explicit delete, cancel, or update tools, but the 24-hour expiration design makes those gaps manageable.

Resources