Skip to main content
Glama

inbin

by io.github.yaotsakpo
OverviewDiscussionsAdmin

create_trial_inbox

Create a temporary inbox with NO Inbin account required at all -- usable before the human has signed up for anything. Returns the inbox address IMMEDIATELY; it does not wait for anything. Use the address to sign up wherever you need a confirmation sent, THEN call await_trial_inbox with that same address to block for the confirmation -- calling this alone does not get you a confirmation. This inbox is NOT tied to any account yet and expires automatically within about two weeks regardless of use. If the human wants to keep using this SAME address permanently, call claim_trial_inbox: no dashboard visit, no key to copy, and more than one agent can independently connect to the same address over time this way.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
purpose_labelNoOptional human-readable label for what this inbox is for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / expected_sender
      Removed value: -{
-  "description": "Glob on the sender address, e.g. *@vercel.com.",
-  "type": "string"
-}
    • removedInput schema / properties / ttl_seconds
      Removed value: -{
-  "default": 45,
-  "maximum": 60,
-  "minimum": 1,
-  "type": "integer"
-}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and idempotentHint=false. The description adds substantial context beyond that: it returns the address immediately without waiting, the inbox is unbound to any account, it auto-expires in roughly two weeks regardless of use, and it grants no confirmation on its own.

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?

Content is front-loaded, with the immediate-return and no-account traits stated first, then the workflow, then the expiry and claim path. Slightly verbose with heavy capitalization for emphasis, but essentially every sentence carries distinct information.

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?

Even with no output schema, the description explains what comes back (the address, immediately) and covers lifetime, account binding, and the follow-up calls an agent must make. Nothing needed to invoke this correctly is missing.

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?

Only one optional parameter (purpose_label) with 100% schema description coverage, so the schema already documents it fully. The description adds no further parameter meaning, but the zero-required-param shape means there is little to explain.

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 precise verb+resource ('Create a temporary inbox') and immediately characterizes the key distinguisher: no account required, usable before signup. An agent can tell this apart from await_trial_inbox and claim_trial_inbox without opening any schema.

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?

Explicitly describes the workflow: use the returned address to sign up, THEN call await_trial_inbox to block for the confirmation, and warns that calling this alone does not yield a confirmation. It also names claim_trial_inbox as the alternative when the address must be kept permanently.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All inbin toolsInspect
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.

Resources