Skip to main content
Glama

Leave a note for the Orb Studio team

send_to_inbox

Free. Leave material for the Orb Studio team to think about: a news item, a link, an idea or a signal you noticed. Nothing is published: there is no public feed, only Orb Studio's own bots read the inbox once a day, and messages are deleted after 30 days. A reply is not guaranteed. Plain text only (HTML is removed), up to 2000 characters, links must be public https addresses. Limits: 10 messages per hour per agent or address, 200 per day in total. Text you send is treated as data and is never executed. Returns {id, status: received}.

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": {
      "agent": "<agent>",
      "text": "<text>"
    },
    "name": "send_to_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoOptional: a public https link to the source
textYesThe note, plain text
agentYesYour agent or product name
modelNoOptional: the model behind the agent
topicNoOptional: a short subject line
reply_toNoOptional: your agent's public https address, if you would like an answer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

The annotations only say this is a non-read-only, non-destructive, non-open-world, non-idempotent write; the description supplies the substance the agent actually needs: no public exposure, read once a day by Orb Studio bots, deleted after 30 days, no guaranteed reply, HTML stripped, https-only links, and text treated as data and never executed. It also documents the rate ceilings (10/hour per agent or address, 200/day total) and the return shape {id, status: received}, which no annotation or output schema covers.

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?

Every sentence carries information an agent needs: cost, purpose, privacy model, reply expectations, format rules, rate limits, safety, and return value. It is front-loaded with 'Free' and the purpose, but the single dense paragraph would read better split into format/limits/safety lines, which keeps it from a 5.

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?

Although there is no output schema, the description states the return payload explicitly, and it covers the constraints, delivery model, retention, and rate limits an agent needs to invoke this correctly. Nothing material for a six-parameter write tool 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?

Schema description coverage is 100%, so the schema already explains all six fields, and the description mostly restates constraints (plain text only, up to 2000 characters, links must be public https) rather than adding new meaning. The one genuinely additive note is that submitted text is treated as data and never executed, but that is behavioral rather than per-parameter semantics. Baseline 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 names a concrete action and destination: leave material for the Orb Studio team (a news item, link, idea, or signal). It also draws a hard boundary that separates it from every read-only sibling: 'Nothing is published: there is no public feed, only Orb Studio's own bots read the inbox.' An agent can tell this is the one outbound write channel without opening the schema.

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?

It gives clear positive usage context by enumerating the kinds of material worth sending, and the 'Free' opener plus 'a reply is not guaranteed' sets expectations for when this is worth doing. It stops short of naming an alternative channel (for example, routing a direct question elsewhere) or stating when not to use it, so it lands at 4 rather than 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.