Skip to main content
Glama

Cherami

by to.cherami
OverviewDiscussionsAdmin

Create inbox

create_inbox

Create an @cherami.to inbox at an address the human or the assignment authorizes.

Input Schema

NameRequiredDescriptionDefault
nameNoOptional internal name, visible across the account but not to recipients. At most 256 UTF-8 bytes.
local_partYesThe part before @cherami.to, permanent once created: 1–64 ASCII letters, digits, hyphens or underscores, starting and ending with a letter or digit. Lowercased.
sender_nameNoOptional display name recipients see on outgoing mail. At most 256 UTF-8 bytes.
idempotency_keyNoMakes a retry safe: repeating the call with the same key and identical arguments within 24 hours of the first request returns the inbox already created. Use a new key for each intended inbox.

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
addressYes
replayedNo
created_atYesAbsolute ISO 8601 service timestamp in UTC (Z), with millisecond precision.
local_partYes
sender_nameYes
idempotency_expires_atNoUntil this time, a retry with the same idempotency_key returns this inbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Retain a unique key, exact payload and first request time per intended creation. Reuse only within 24 hours; replay returns the inbox's current names."New value: +"Makes a retry safe: repeating the call with the same key and identical arguments within 24 hours of the first request returns the inbox already created. Use a new key for each intended inbox."
    • changedInput schema / properties / local_part / description
      Previous value: -"Immutable part before @cherami.to; 1–64 letters, numbers, hyphens and underscores after trimming, with alphanumeric ends. Lowercased on creation."New value: +"The part before @cherami.to, permanent once created: 1–64 ASCII letters, digits, hyphens or underscores, starting and ending with a letter or digit. Lowercased."
    • changedInput schema / properties / name / description
      Previous value: -"Optional internal inbox name shared by the account; not the public sender identity. At most 256 UTF-8 bytes."New value: +"Optional internal name, visible across the account but not to recipients. At most 256 UTF-8 bytes."
    • changedInput schema / properties / sender_name / description
      Previous value: -"Optional public name recipients see on subsequent outgoing mail. At most 256 UTF-8 bytes."New value: +"Optional display name recipients see on outgoing mail. At most 256 UTF-8 bytes."
    • changedOutput schema / properties / idempotency_expires_at / description
      Previous value: -"End of creation-key protection; do not retry uncertain creation after this instant."New value: +"Until this time, a retry with the same idempotency_key returns this inbox."
  2. Changed1 schema field changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Retain a unique key, exact payload and first request time per intended creation. Reuse only within 24 hours; replay returns current names, not the original settings."New value: +"Retain a unique key, exact payload and first request time per intended creation. Reuse only within 24 hours; replay returns the inbox's current names."
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/non-destructive profile is known. The description adds that the address must be authorized, but omits permanence, idempotency behavior (though in schema), uniqueness constraints, and what happens on conflict — a gap for a creation tool.

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?

A single tight sentence that front-loads the verb, resource, and domain. Every clause (authorization requirement) earns its place.

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

Completeness3/5

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

With an output schema present and 100% param coverage, the description needn't explain return values. However, for a creation tool with no exclusive behavior from annotations beyond safety, the absent permanence, conflict, and uniqueness context leaves an agent needing more than the one-liner supplies.

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 description coverage is 100%, so the schema already fully documents local_part, name, sender_name, and idempotency_key with formats and constraints. The description adds no parameter-level detail beyond what the schema provides, which is the correct baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (create) and resource (inbox) with the domain address @cherami.to. Siblings include create_draft, delete_inbox, update_inbox, so the create action is distinguishable, but the description doesn't differentiate from those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage through the authorization caveat ('at an address the human or the assignment authorizes'), but gives no explicit when-to-use vs create_draft or other siblings, and no exclusions or alternatives.

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

All Cherami 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