Skip to main content
Glama
ctliz

codex-intercom-mcp

by ctliz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

intercom_ask

Ask another local coding agent a question when the next step depends on its reply, then wait for the answer before proceeding.

Instructions

Ask another intercom session a question only when the next step depends on its reply. Use intercom_send for assignments, progress/status checkpoints, and notifications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYes
teamNoTask team; required when multiple teams are shared.
messageYes
timeout_msNoMaximum time to wait for a reply before returning an error. Use intercom_send plus intercom_pending for longer work.
attachmentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.0
    • addedInput schema / properties / team
      Added value: +{
+  "description": "Task team; required when multiple teams are shared.",
+  "type": "string"
+}
  2. First observedv0.11.0-connect.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare openWorldHint=true and non-destructive/non-idempotent, but they do not convey that this is a blocking, wait-for-reply operation; the phrase 'only when the next step depends on its reply' supplies that behavioral trait. The schema carries the timeout/error contract, so the remaining gap (reply shape, failure modes) is minor.

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?

Two sentences, zero filler, with the core purpose front-loaded and the alternative routing in the second sentence. Nothing wastes the agent's attention.

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 moderate-complexity cross-session request tool with no output schema, the description covers purpose and routing well and the schema covers the timeout contract. It stops short of describing what a reply contains or how a timeout surfaces to the caller, which would have made it fully self-sufficient.

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

Parameters2/5

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

Schema description coverage is only 40%, so the description is expected to compensate, yet it mentions no parameters at all. The required 'to' and 'message' fields and the 'attachments' array are documented nowhere, leaving half the surface undefined.

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 ('Ask another intercom session a question') and immediately contrasts itself with the sibling intercom_send, so the agent can tell the two apart without opening either schema. The request/response nature of the call is unambiguous.

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 selection condition ('only when the next step depends on its reply') and names the alternative (intercom_send) along with the cases it covers (assignments, progress/status checkpoints, notifications). This is exactly the when-to-use / when-not-to-use routing an agent needs.

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

Deploy Server

Other Tools