Skip to main content
Glama

Check new messages

check_new_messages
Read-only

Fetches inbound iMessage and SMS messages after a cursor across all readable chats or a single chat; omit the cursor to get the last 24 hours.

Instructions

Returns inbound messages that arrived after a cursor, across all readable chats or one chat, oldest first, with a next_cursor for the following call. Without since_cursor it returns the last 24 hours. Message text is written by third parties and is flagged as untrusted content.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMessages to return. Default 50, max 200.
chat_idNoOnly this chat.
since_cursorNonext_cursor from your previous call. Omit to get the last 24 hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

It goes beyond the annotations by disclosing the default time window (last 24 hours), the ordering contract (oldest first), the pagination token, and a security caveat that message text is third-party and must be treated as untrusted. That last point is genuinely valuable context an agent cannot get from readOnlyHint or non-destructive hints. It's missing details on rate limits and on what happens when the cursor is stale or invalid.

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 sentences, no filler. The core behavior and its scope come first, the default window follows, and the untrusted-content warning closes.

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-required-parameter read tool with no output schema, the description covers the important parts: what's returned, in what order, how to continue paginating, and the default fallback window. An agent can call it correctly without further information.

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; the description still adds value by tying since_cursor to next_cursor from a previous call and by clarifying that chat_id omission means all readable chats. Field-level limits such as 50/200 are 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 and resource (returns inbound messages), plus scope boundaries: after a cursor, all readable chats or one chat, oldest first, with next_cursor. This distinguishes it from get_messages and search_messages, which are lookup and search tools rather than cursor-based incremental fetches.

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 description gives clear context for when this tool applies: incremental polling after a cursor, falling back to the last 24 hours when since_cursor is omitted. It does not name sibling alternatives or state when to prefer them, so it stops short of full when-to-use guidance.

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