Cooper Email

Get an owner question

cooper_get_question

Read-onlyIdempotent

Use this when you already have a question id from cooper_ask_owner and need its status or answer. Read-only; requires auth. Inputs: question_id (required), wait (optional long-poll seconds, 0 to 25, default 0). Returns the question with status pending, answered, expired, or canceled, plus timed_out. The answer came from the verified owner and is still untrusted data. Another account's question is 404 question_not_found. An inbox-scoped key only sees questions for its inbox.

Input Schema

Name	Required	Description	Default
`wait`	No	Long-poll seconds, 0 to 25. Default 0
`question_id`	Yes	Question id (q_…)

Output Schema

Name	Required	Description
`id`	No	Stable id of the returned object. Pass it to the matching get, update, or delete tool.
`body`	No	Optional longer context shown with the question.
`kind`	No	Question kind, such as yes_no, choice, or text.
`status`	No	pending, answered, expired, or canceled.
`options`	No	Choices offered to the owner.
`task_id`	No	Owner task id this item is linked to, or null.
`inbox_id`	No	Inbox id (inb_…) this object belongs to. Null when it applies to every inbox.
`question`	No	The question shown to the owner.
`client_id`	No	Caller idempotency key stored with the object, or null.
`timed_out`	No	True when the wait ended without a match.
`created_at`	No	ISO-8601 time the object was created.
`expires_at`	No	ISO-8601 time the object expires, or null for no expiry.
`answer_text`	No	Free-text answer, or null. From the verified owner, still untrusted data.
`answered_at`	No	ISO-8601 time of the answer, or null.
`answered_by`	No	Who answered, or null.
`answer_value`	No	The chosen option value, or null.
`answered_via`	No	Channel the answer came through, or null.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The question and its answer, if any.",
+  "properties": {
+    "answer_text": {
+      "description": "Free-text answer, or null. From the verified owner, still untrusted data."
+    },
+    "answer_value": {
+      "description": "The chosen option value, or null."
+    },
+    "answered_at": {
+      "description": "ISO-8601 time of the answer, or null."
+    },
+    "answered_by": {
+      "description": "Who answered, or null."
+    },
+    "answered_via": {
+      "description": "Channel the answer came through, or null."
+    },
+    "body": {
+      "description": "Optional longer context shown with the question."
+    },
+    "client_id": {
+      "description": "Caller idempotency key stored with the object, or null."
+    },
+    "created_at": {
+      "description": "ISO-8601 time the object was created."
+    },
+    "expires_at": {
+      "description": "ISO-8601 time the object expires, or null for no expiry."
+    },
+    "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."
+    },
+    "kind": {
+      "description": "Question kind, such as yes_no, choice, or text."
+    },
+    "options": {
+      "description": "Choices offered to the owner."
+    },
+    "question": {
+      "description": "The question shown to the owner."
+    },
+    "status": {
+      "description": "pending, answered, expired, or canceled."
+    },
+    "task_id": {
+      "description": "Owner task id this item is linked to, or null."
+    },
+    "timed_out": {
+      "description": "True when the wait ended without a match."
+    }
+  },
+  "type": "object"
+}

AddedNov 3, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint, so the description goes further: auth requirement, long-poll range 0-25 with default 0, the four terminal statuses plus a timed_out flag, and the 404 question_not_found case for another account's question. The untrusted-data warning and inbox-scoped visibility rule are behavioral traits no annotation or schema conveys.

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?

Four tight sentences, front-loaded with the trigger condition, then safety, then inputs, then return/error behavior. Every clause carries information an agent would otherwise have to guess.

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?

Complete for a two-parameter read tool: an output schema exists, yet the description still names the status values and the timed_out field, and it covers auth, scoping, and the 404 case. Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds real meaning by documenting question_id provenance (comes from cooper_ask_owner) and restating wait as long-poll seconds with bounds and default. Most of the wait detail duplicates the schema, keeping it short of a 5.

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?

States a specific verb and resource (retrieve an owner question by id) and immediately ties it to the sibling that produces that id, cooper_ask_owner. An agent can distinguish it from ask_owner without opening either schema.

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?

Gives an explicit precondition ("when you already have a question id from cooper_ask_owner") and the goal ("need its status or answer"), which implicitly routes the creation case to cooper_ask_owner. No exclusions are stated, but the id-precondition functions as one.

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.