Skip to main content
Glama
ctliz

codex-intercom-mcp

by ctliz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

intercom_join

Create or join a task team after approval, adding connected peers in one call. Omit the team name to list joinable teams.

Instructions

After user approval, create or join a task team. Membership is additive; members lets the manager add connected peers in one call. Omit name to list teams.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoTeam name to join. Omit to list joinable teams.
workNoTask description when creating a team.
createNoCreate this named team and join as manager. Requires name.
membersNoConnected session names or IDs to add; manager only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.13.0
    • addedInput schema / properties / members
      Added value: +{
+  "description": "Connected session names or IDs to add; manager only.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / work
      Added value: +{
+  "description": "Task description when creating a team.",
+  "maxLength": 2000,
+  "type": "string"
+}
  2. Addedv0.12.1

TDQS

A4/5.0
Behavior4/5

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

Annotations cover the safety profile (write, open-world, non-idempotent, non-destructive), and the description adds genuinely new context: a consent prerequisite and the key behavioral trait that 'Membership is additive' rather than replacing. It does not describe error behavior or what join does when the team is absent.

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?

Three short sentences, front-loaded with the approval precondition and the create/join/list modes. No filler; every clause carries an instruction or constraint.

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 four-parameter mutation tool with no output schema, the description covers modes, prerequisites, and the additive-membership semantics. Remaining gaps (return shape for the list mode, failure behavior) are minor.

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%, so the schema already documents all four parameters including the manager-only constraint on members and the create/name dependency. The description largely restates this ('members lets the manager add connected peers', 'Omit name to list teams'), so it adds little beyond the baseline.

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?

States specific verbs and resource: 'create or join a task team', plus a third mode ('Omit name to list teams'). This is clear, though it does not explicitly differentiate itself from the sibling intercom_team, which plausibly overlaps.

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?

Gives a precondition ('After user approval') and a mode-switch rule ('Omit name to list teams'), plus who may pass members ('the manager'). No explicit alternatives are named against the sibling tools, so it stops short of a 5.

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