Skip to main content
Glama
iambashar

agent-intercom

by iambashar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Read new messages

mail_check

Retrieve unread agent messages addressed to you, oldest first. Optionally wait up to 300 seconds for new mail; reading consumes each message and moves it to your read folder.

Instructions

Fetch the unread messages addressed to you ("agent"), oldest first. Use it when you expect a reply or want to see if another agent wrote to you. Reading consumes the messages: each one is moved to your read folder and is not returned again, so act on or note what you need. With wait_seconds above 0 the call blocks until at least one message arrives or the time runs out. Returns each message as "[] from (re ) at :" followed by its body, or "no new messages". When live push is installed, new mail may already appear in your session without calling this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wait_secondsNoHow long to wait for a message if the inbox is empty, in seconds (0 to 300). 0 returns immediately.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.6
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / wait_seconds / default
      Added value: +0
    • changedInput schema / properties / wait_seconds / description
      Previous value: -"Block up to this long for a message"New value: +"How long to wait for a message if the inbox is empty, in seconds (0 to 300). 0 returns immediately."
    • addedInput schema / properties / wait_seconds / maximum
      Added value: +300
    • addedInput schema / properties / wait_seconds / minimum
      Added value: +0
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Discloses the key non-obvious behavior beyond annotations: reading consumes messages by moving them to a read folder and they are not returned again, blocking semantics of wait_seconds above 0, and the exact return format or 'no new messages'. This is exactly the behavioral context annotations (readOnlyHint=false, idempotentHint=false) gesture at but cannot explain.

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?

Front-loads the core action and scope, then adds consumption warning, blocking behavior, and return format in a tight series of sentences. No filler.

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 one-optional-param tool with no output schema, the description covers ordering, consumption side effect, blocking semantics, return format, and the live-push caveat – everything an agent needs to call it correctly and interpret results.

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 already 100%, so baseline is 3; the description adds the blocking semantics ('blocks until at least one message arrives or the time runs out') which clarifies the practical effect of wait_seconds beyond the schema's 'how long to wait'. It'd be a 5 with a note on the 300s cap, but the schema already states that.

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 (fetch) and resource (unread messages addressed to you), with scope ('agent'), ordering ('oldest first'), and distinguishes itself from siblings by covering inbox consumption rather than peer listing or sending.

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 clear context for when to call it ('when you expect a reply or want to see if another agent wrote to you') and warns that live push may make calling unnecessary, but doesn't explicitly compare against mail_peers or mail_send.

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