Skip to main content
Glama

AI SENSE Free Public Tools

by com.aisenseapi

Read agent inbox

read_agent_inbox
Read-onlyIdempotent

Read the mail that has arrived in an inbox from create_agent_inbox. Each message carries the sender, the subject, the arrival time in UTC, the cleaned text, any standalone 4 to 8 digit codes found in that text and any public http or https links. Attachments and raw headers are not stored. Set wait_seconds from 1 to 25 to wait for the next message, or zero to read immediately. An empty inbox is the ordinary answer before mail arrives and is not a failure. When truncated is true, at least one whole message was refused because the inbox had reached its 20 message cap or its 256 KiB total text cap. A code you are waiting for may then have been turned away rather than delayed. The reply names the public slug and never repeats the secret inbox_id. An unknown inbox_id and a wrong one fail in the same way, so neither can be told from the other, while an expired inbox says that it expired. No API key, account or sign up is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inbox_idYesThe secret UUID that create_agent_inbox returned as inbox_id. Not the slug and not the address.
wait_secondsNoWait up to this many seconds for new mail. Zero returns immediately.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
slugYes
addressYes
messagesYes
receivedYes
truncatedYesTrue once at least one whole message has been refused, by the 20 message cap or by the 256 KiB total text cap. Messages already stored are kept.
wait_reasonYes
waited_secondsYes
expire_timestampYes
created_at_timestampYes

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedOutput schema / properties / messages / items / properties / date / description
      Added value: +"Arrival time in UTC, for example 2026-01-31T09:15:00Z. It records when the mail reached the mailbox, and falls back to the Date header written by the sender only when that arrival time is missing."
    • changedOutput schema / properties / truncated / description
      Previous value: -"True when the inbox was full and refused newer mail."New value: +"True once at least one whole message has been refused, by the 20 message cap or by the 256 KiB total text cap. Messages already stored are kept."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly and idempotent, and the description adds substantial behavioral detail: attachments and raw headers are not stored, 20-message and 256 KiB caps with truncation semantics, the reply uses a public slug and never repeats the secret inbox_id, unknown and wrong inbox_id fail identically while expired inboxes differ, and no API key or account is required. This covers safety, failure modes, and response nuances.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Longer than average, but every sentence carries distinct operational information: content shape, omitted attachments/headers, wait behavior, normal empties, truncation consequences, identifier secrecy, failure indistinguishability, and lack of auth. It is front-loaded with purpose and contains no 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 read tool with readOnly and idempotent annotations, an output schema, and full parameter schema coverage, the description supplies all missing behavioral context an agent needs: caps, truncation, empty semantics, failure modes, and identifier handling. Nothing essential is left unexplained.

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 100%, so the schema already defines both parameters. The description adds value by clarifying wait_seconds behavior, the meaning of an empty result, truncation consequences, and inbox_id secrecy/failure behavior, going beyond the schema without needing to repeat field-level format details.

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 opens with 'Read the mail that has arrived in an inbox from create_agent_inbox', naming a specific verb and resource and referencing the creating sibling. It is clearly the agent-inbox reader, distinct from read_heartbeat, read_human_approval, read_webhook_capture, and read_temporary_data.

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 clear operational guidance: wait_seconds 0 returns immediately, 1 to 25 waits, an empty inbox is a normal pre-delivery result, and truncation means a message may have been refused. It doesn't explicitly contrast with sibling read tools, but the tool name and context make the domain unmistakable.

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