Cooper Email

Get phone number

cooper_get_phone_number

Read-onlyIdempotent

Read the active phone number on an inbox. Requires auth. Input: inbox_id.

Input Schema

Name	Required	Description	Default
`inbox_id`	Yes	Inbox id (inb_…) that owns the phone number. Get it from cooper_list_inboxes.

Output Schema

Name	Required	Description
`id`	No	Stable id of the returned object. Pass it to the matching get, update, or delete tool.
`e164`	No	The phone number in E.164.
`object`	No	Object type name, such as list, message, or thread.
`status`	No	active or released.
`billing`	No	Billing result for this number, such as {status}.
`inbox_id`	No	Inbox id (inb_…) this object belongs to. Null when it applies to every inbox.
`outbound`	No	Outbound SMS registration state. Sends fail with outbound_not_registered until it is ready.
`provider`	No	Carrier provider name.
`account_id`	No	Cooper account id (acct_…) that owns this object.
`created_at`	No	ISO-8601 time the object was created.
`number_type`	No	Number type, such as local.
`released_at`	No	ISO-8601 time the number was released, or null.
`capabilities`	No	What the number supports, such as sms and voice.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / inbox_id / description

Added value: +"Inbox id (inb_…) that owns the phone number. Get it from cooper_list_inboxes."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The active phone number on the inbox.",
+  "properties": {
+    "account_id": {
+      "description": "Cooper account id (acct_…) that owns this object."
+    },
+    "billing": {
+      "description": "Billing result for this number, such as {status}."
+    },
+    "capabilities": {
+      "description": "What the number supports, such as sms and voice."
+    },
+    "created_at": {
+      "description": "ISO-8601 time the object was created."
+    },
+    "e164": {
+      "description": "The phone number in E.164."
+    },
+    "id": {
+      "description": "Stable id of the returned object. Pass it to the matching get, update, or delete tool."
+    },
+    "inbox_id": {
+      "description": "Inbox id (inb_…) this object belongs to. Null when it applies to every inbox."
+    },
+    "number_type": {
+      "description": "Number type, such as local."
+    },
+    "object": {
+      "description": "Object type name, such as list, message, or thread."
+    },
+    "outbound": {
+      "description": "Outbound SMS registration state. Sends fail with outbound_not_registered until it is ready."
+    },
+    "provider": {
+      "description": "Carrier provider name."
+    },
+    "released_at": {
+      "description": "ISO-8601 time the number was released, or null."
+    },
+    "status": {
+      "description": "active or released."
+    }
+  },
+  "type": "object"
+}

AddedOct 17, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds only two small facts beyond that: the number returned is the 'active' one, and authentication is required. It says nothing about what happens when no number is provisioned.

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?

Three short sentences, front-loaded with the action and scope. The trailing 'Input: inbox_id' segment is largely wasted since the required parameter is already declared in the schema.

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?

An output schema exists, so return values need no explanation, and the tool is a simple single-parameter getter. Still, edge behavior such as what is returned or raised when an inbox has no active number is left unstated, which is the main remaining gap for an agent.

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% and the schema itself explains the inb_… format and points to cooper_list_inboxes for discovery. The description merely restates 'Input: inbox_id', adding no meaning beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource ('Read the active phone number') scoped to an inbox, which is enough to separate it from provisioning or releasing a number. It stops short of naming the siblings cooper_provision_phone_number or cooper_release_phone_number, so the differentiation is implicit rather than explicit.

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?

'Requires auth' gives one prerequisite, and 'on an inbox' implies the lookup is keyed by an existing inbox. There is no statement of when to prefer this over cooper_get_inbox or cooper_list_inboxes, and no when-not guidance, so usage is only implied.

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

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