Skip to main content
Glama

owner_contact_thread

Read or choose YOUR contact chat in this workspace: the conversation that gets owner.ask questions (when you are the workspace owner) and the notices that need a person (an agent paused, a session not answering). With no parameters it answers what is in force. thread_id chooses any conversation of this workspace, for example a team group the workspace's bot is in, so questions are asked where the people who decide read them; an answer written there by a workspace member (a reply to the question, or the option's number) comes back to the asking agent. clear: true goes back to the automatic choice (your own chat with a workspace bot, else e-mail). A chat that is not your own needs the member, admin or owner role, and an agent in its own run cannot choose. Do not choose a customer's conversation: every question and notice would be sent into it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "owner_contact_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearNotrue: drop the choice, the automatic one applies.
thread_idNoThe conversation to write to you in (its thread id in this workspace's inbox).
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations are shallow (readOnlyHint=false, destructiveHint=false, idempotentHint=false) and the description carries the real burden: the permission model, the in-run restriction, what clear reverts to, and the consequence that replies written in the chosen thread route back to the asking agent. It stops short of stating the return shape or whether a later auto-choice change silently overwrites the selection.

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?

Purpose is front-loaded and each parameter mode follows in call order, with the safety warning last. The middle sentence about routing answers is long and clause-heavy, but it is not padding and no sentence is purely redundant.

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?

For a 3-optional-parameter configuration tool with no output schema, the description covers selection, reversion, permissions, and side effects on where questions are delivered. The only gap is what the no-parameter read actually returns, which is gestured at ('answers what is in force') rather than described.

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, but the description genuinely adds meaning: thread_id is illustrated with a concrete use case (a team group the bot is in) and its downstream effect on where answers land, and clear is explained as reverting to 'your own chat with a workspace bot, else e-mail'. Only in_workspace is left to the schema.

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 pair and resource ('Read or choose YOUR contact chat') and immediately scopes it to 'the conversation that gets owner.ask questions' and to notices needing a person, which separates it from owner_ask and the agents_* siblings. An agent can identify the resource and its role 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit call modes (no parameters = read what is in force; thread_id = choose a conversation; clear:true = revert to the automatic choice) plus preconditions (member/admin/owner role for a chat that is not your own, an agent in its own run cannot choose) and an explicit prohibition ('Do not choose a customer's conversation'). This is when/when-not plus alternatives territory.

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.