Skip to main content
Glama
Sign In

Cooper Email

by com.cooperemail
OverviewDiscussionsAdmin

Join an owner chat

cooper_chat_join

Join a human's Cooper chat with a pair code. Without a key, this creates an account, an inbox, and an API key (returned once). With a key, it links that key's inbox. An account-wide key must pass inbox_id. A key limited to one inbox uses that inbox. The owner's full email is not returned.

Input Schema

NameRequiredDescriptionDefault
codeYesPair code the human copied from their Cooper chat screen.
inbox_idNoInbox id (inb_…) to link when an account-wide key is sent. Not needed without a key or with a key limited to one inbox.
usernameNoOptional local part for the new inbox when this call creates an account. Omit and Cooper picks one. Ignored when a key is sent.
display_nameNoOptional From name for the new inbox when this call creates an account.

Output Schema

NameRequiredDescriptionDefault
inboxNo{id, email, display_name} of the linked inbox.
objectNoObject type name, such as list, message, or thread.
api_keyNoAPI key, returned only once when this call created the account. Never repeat it in full.
owner_email_maskedNoThe owner's address with most characters hidden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / code / description
      Added value: +"Pair code the human copied from their Cooper chat screen."
    • addedInput schema / properties / display_name / description
      Added value: +"Optional From name for the new inbox when this call creates an account."
    • addedInput schema / properties / inbox_id / description
      Added value: +"Inbox id (inb_…) to link when an account-wide key is sent. Not needed without a key or with a key limited to one inbox."
    • addedInput schema / properties / username / description
      Added value: +"Optional local part for the new inbox when this call creates an account. Omit and Cooper picks one. Ignored when a key is sent."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The linked inbox, and a new API key when this call created the account.",
+  "properties": {
+    "api_key": {
+      "description": "API key, returned only once when this call created the account. Never repeat it in full."
+    },
+    "inbox": {
+      "description": "{id, email, display_name} of the linked inbox."
+    },
+    "object": {
+      "description": "Object type name, such as list, message, or thread."
+    },
+    "owner_email_masked": {
+      "description": "The owner's address with most characters hidden."
+    }
+  },
+  "type": "object"
+}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare non-readonly, non-idempotent, non-destructive, closed-world; the description adds the substantive behavior: this may silently create an account, an inbox, and an API key, and the key is returned only once. It also discloses a privacy detail (owner's full email not returned). It does not say what happens on an invalid or already-consumed pair code, which would complete the picture.

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?

Four short sentences, front-loaded with the core action and immediately followed by the conditional paths; no filler. The telegraphic phrasing ("With a key, it links that key's inbox") is efficient, though the mode-switching could be structured more explicitly for a reader scanning conditions.

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

Completeness4/5

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

An output schema exists, so return values need not be described, and the description still flags the one-time API key and withheld email. Annotations cover the safety profile. What is missing is failure-mode behavior (expired/invalid code, repeat joins), which matters for a non-idempotent account-creating call.

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 documents code, inbox_id, username, and display_name, including the 'ignored when a key is sent' caveat. The description restates the same conditional logic at a high level rather than adding format, validation, or constraint detail beyond it. Baseline 3 applies when the schema carries the parameter burden.

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?

The description gives a specific verb and resource ("Join a human's Cooper chat with a pair code") and immediately explains the two operating modes: no key creates an account/inbox/API key, a key links that key's inbox. That is far more than a restatement of the title. It does not name sibling tools such as cooper_onboard, cooper_create_inbox, or cooper_wait_for_code, so the agent must infer the boundary itself.

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 clearly states the conditions that select each path: no key = account creation, key present = link, account-wide key = must pass inbox_id, inbox-limited key = uses that inbox. This is real branching guidance rather than vague context. It stops short of explicit exclusions or naming an alternative tool for related flows, so it is not a 5.

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

All Cooper Email 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