Skip to main content
Glama
Zulip MCP Server
by ahmadjan223

zulip_get_my_mentions

Retrieve messages that @-mention this bot or are direct messages to it across all channels, optionally only newer than a given message ID, with sender and topic details.

Instructions

Get messages that @-mention this bot or are direct messages to it, across all channels. Pass since_message_id (the highest id you've already handled) to get only newer ones. Returns plain-text messages with id, channel, topic and sender, oldest first.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax messages to return (default 20)
since_message_idNoOnly return messages with an id greater than this (omit for the latest ones)

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?

With no annotations, the description carries the full burden, and it delivers: it discloses the result shape (plain-text messages with id, channel, topic, sender), the ordering (oldest first), and the cursor semantics that make incremental polling safe. It does not mention auth requirements, rate limits, or what happens when nothing new exists, leaving minor gaps.

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, each doing distinct work: identity, incremental-fetch instruction, return shape and ordering. The most decision-relevant content (what it returns and how to poll) is front-loaded with 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 two-parameter read tool with no output schema and no annotations, the description supplies everything needed to call it correctly, including a stand-in for the missing output schema by naming the returned fields and their order. Nothing material is left for the agent to guess.

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 earns above that by explaining the polling idiom for since_message_id ("the highest id you've already handled"), which is meaning the schema's "id greater than this" does not convey. The limit parameter is left to the schema, which is acceptable given full coverage.

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 uses a specific verb and resource ("Get messages that @-mention this bot or are direct messages to it") and states the scope ("across all channels"). An agent can distinguish this personal-inbox tool from zulip_get_channel_history or zulip_get_topics without inspecting either schema.

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?

It gives concrete operating guidance: pass since_message_id (the highest id already handled) to fetch only newer messages, which tells the agent this is the polling/incremental tool. It stops short of explicitly naming when to prefer a sibling like zulip_get_channel_history, so no exclusion rule is stated.

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