Skip to main content
Glama
Sign In
codex-intercom-mcp

codex-intercom-mcp

by ctliz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

intercom_whoami

Read-onlyIdempotent

Retrieve your current Codex session's Intercom identity, enabling other coding agents to target messages to this session accurately.

Instructions

Return this Codex session's intercom identity for reliable targeting.

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": "intercom_whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0-connect.1

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the returned identity is meant for targeting, but it does not disclose the return format or any further behavioral details.

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?

One sentence with no wasted words. The key information is front-loaded: what the tool returns and why it is useful.

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 a no-parameter, read-only identity lookup, the description is sufficient. It clearly tells the agent what the tool produces and why that output matters, and no additional invocation guidance is needed.

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?

The tool has zero parameters and 100% schema coverage, so the parameter semantics burden is minimal. The baseline for a zero-parameter tool is 4, and the description does not need to explain parameter behavior.

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 ('Return'), a specific resource ('this Codex session's intercom identity'), and a clear purpose ('for reliable targeting'). This distinguishes it from the sibling intercom tools, which handle other actions like sending, replying, or listing.

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?

The phrase 'for reliable targeting' gives clear context for when to call this tool: before actions that need to address the current session. However, it does not explicitly name alternatives or state when not to use it.

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