Skip to main content
Glama

owner_ask

Ask the workspace owner a question when you cannot decide something yourself. The owner gets ONE message where they actually are (their messenger, else e-mail) and the question is kept as a task on the board. This call does NOT wait: it returns at once, so name a safe default (for example the option that sends nothing) and continue your work on it. The answer comes back later as an owner_answered event that starts the asking agent through its own trigger, and is always written as a comment on the task. Never put the question into a customer's conversation, and never stop to wait for a person at a terminal.

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": {
      "question": "<question>"
    },
    "name": "owner_ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
defaultNo1-based number of the option that applies when no answer comes in time. Pick the safe one.
optionsNoUp to 9 answers to pick from. The owner replies with the number.
task_idNoAttach the question to this existing task instead of creating one. The task's status and assignee are not changed.
agent_idNoAsk as this agent: it is the one started with the answer. A session passes its own agent's id.
questionYesThe question, in the owner's language, with what they need to decide in the text itself.
expires_inNoHow long to wait: "30m", "24h" (default), "3d". Between 5 minutes and 14 days.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
context_thread_idNoThe conversation the question is about. Kept on the task as context; the question is never sent there.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

The description goes well beyond the annotations, which only say it is non-destructive, non-open-world, non-idempotent and not read-only. It discloses that the call does NOT block, that the owner receives exactly ONE message routed to messenger with e-mail fallback, that the question persists as a board task, and that the reply arrives later as an owner_answered event that re-triggers the asking agent and is recorded as a comment. That is exactly the async/event semantics an agent needs and cannot get from the schema.

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 sentences, front-loaded with purpose, then non-blocking behavior, then the return path, then the hard exclusions. Every sentence carries information and the ordering is sensible. It is dense but not padded, though the async-return explanation is spread across two sentences and could be tighter.

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?

For an 8-parameter, non-blocking, non-idempotent mutation with no output schema, the description covers the full lifecycle: send, don't wait, fall back to default, receive answer as an event, answer also lands as a task comment. Nothing essential to calling it correctly is missing, and the missing output schema is compensated by the explicit explanation of how the answer returns.

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 earns above that by explaining why `default` matters ('this call does NOT wait... so name a safe default, for example the option that sends nothing') and by tying the delayed answer to the `default` fallback path. It adds intent-level meaning rather than restating field descriptions.

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 opens with a concrete verb and resource — 'Ask the workspace owner a question' — and immediately scopes it with 'when you cannot decide something yourself.' An agent can picture the action without opening the schema. It stops short of naming the sibling it replaces (e.g. agents_ask), so differentiation relies on inference rather than explicit routing.

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?

Usage is well framed: use it when blocked on a decision, name a safe default, and keep working. Two explicit exclusions are given ('never put the question into a customer's conversation', 'never stop to wait for a person at a terminal'), which is real when-not guidance. It never names an alternative tool for the cases where a different ask mechanism might be appropriate.

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.