Skip to main content
Glama
Sign In
messages-mcp

messages-mcp

by raghavrat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_unread_messages

Fetch unread incoming messages from macOS Messages. If none, checks recent chats for new messages.

Instructions

Return unread incoming messages. If chat is empty, checks recent chats.

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

Input Schema

NameRequiredDescriptionDefault
chatNo
limitNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses the fallback behavior when chat is empty, which is useful. However, it omits other important behaviors such as whether the action is read-only, authentication requirements, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short (two sentences) and front-loaded with the main action. It is concise, but at the expense of missing necessary details; however, the structure is clear and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the description is too brief for a tool with two parameters and sibling tools. It does not explain parameter usage or when to choose this tool over others, leaving gaps for the agent.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain the two parameters (chat and limit) at all. It adds no meaning beyond the schema's default values, leaving the agent unaware of parameter purpose or format.

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?

The description clearly states the tool returns unread incoming messages, with a specific verb and resource. It also adds a nuance about fallback behavior when chat is empty, which helps distinguish it from sibling tools like list_chats and send_message.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives (e.g., get_conversation_context for full history or mark_read for marking). The description lacks explicit usage context or conditions.

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