Inbin agent meetings

claim_trial_inbox

Start connecting an agent to this inbox address, permanently -- the SAME address. Works whether this is a brand-new trial inbox OR one that's already been claimed by a different agent before: more than one agent can independently connect to the same inbox, each getting its own separate, revocable connection. Returns a claim_url immediately -- share it in chat right away. The human clicks it, enters their email, enters the one-time code Inbin sends there, and a credential is ISSUED. That is NOT the same as the connection working yet -- the human still has to install that credential into an MCP client's config before anything can actually use it, and you will never see the credential itself, by design. Call await_trial_inbox_claim afterward to see the human finish the email+code step, then claim_connection_status (repeatedly, possibly much later -- installing a client is not instant) to see whether a client has actually started using it. The inbox must still exist (not yet expired) for this to work; it does not need to still be a TRIAL inbox specifically.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "inbox_address": "<inbox_address>"
    },
    "name": "claim_trial_inbox"
  }
}

Input Schema

Name	Required	Description	Default
`inbox_address`	Yes	The exact inbox address to connect to, e.g. abc123@in.inbin.dev.
`connector_label`	No	Optional label identifying which agent/client is connecting, e.g. 'Research assistant'. Shown to the human as the name of this specific connection so they can tell multiple connections apart later.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), it discloses that a claim_url is returned immediately, that the human must click and enter an emailed one-time code, that a credential is issued but that credentials are never visible to the agent by design, and that multiple agents can hold independent revocable connections. This does useful work that the annotations do not, though it doesn't specify failure modes such as an expired or invalid address.

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?

It is front-loaded with the core action and the immediate claim_url return, and the sequencing information is ordered logically. It is somewhat long with heavy em-dash and capitalization emphasis, but most sentences carry distinct operational 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?

For a two-parameter mutation with no output schema, the description supplies the return value (claim_url), the human-side workflow, the credential-installation caveat, and the follow-up tool sequence. An agent has everything needed to invoke it and interpret the result 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%, so both inbox_address and connector_label are already fully documented in the schema, and the description adds little parameter-specific detail. It does clarify that the address must still exist and not be expired, which slightly augments the inbox_address meaning.

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 ('Start connecting an agent to this inbox address') and scopes it precisely as a persistent connection to the same address. It also distinguishes the tool from siblings by naming await_trial_inbox_claim and claim_connection_status as follow-on steps.

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?

It explicitly says to call await_trial_inbox_claim afterward, then claim_connection_status repeatedly (possibly much later). It also covers edge cases: works for a brand-new trial inbox or one already claimed, and the inbox must still exist but need not still be a trial.

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

All Inbin agent meetings 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.