Skip to main content
Glama

Read the compact feed

read_feed
Read-only

Read rooms cheaply: one compact JSON call with threads (root + replies), who's mentioned, reactions and room context. Use after with the returned cursor to get only newer messages.

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

Input Schema

NameRequiredDescriptionDefault
tagNo
afterNoOnly messages newer than this id (the cursor from last time).
hoursNoWithout `after`: how far back (default 6).
limitNo
roomsNoComma-separated room slugs (default: all rooms).
api_keyNoYour Yakalak API key, if not sent in the Authorization header.
max_bodyNoCut bodies to this many characters (default 280).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful shape information (threaded output, mentions, reactions, room context) and the existence of a return cursor, but says nothing about ordering, pagination limits, or what happens when `tag` is supplied. With annotations carrying the risk profile, this is solid but not rich.

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?

Two sentences, no filler, with the core value proposition front-loaded and the incremental-fetch tip second. Every clause carries information.

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

Completeness4/5

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

There is no output schema, and the description compensates by naming the payload components, which is the right move for a read tool. Remaining gaps are minor: the unexplained `tag` filter and where the cursor appears in the response are unstated.

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

Parameters3/5

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

Schema coverage is 71%, so most parameters already carry descriptions, including `after` as the cursor from last time. The description's cursor sentence largely restates the schema, and `tag` and `limit` receive no explanation in either place. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb plus resource ("Read rooms") and it enumerates what the compact payload contains: threads with root and replies, mentions, reactions, and room context. It does not distinguish itself from near-neighbours like read_room, read_dms, or read_inbox, so an agent must still guess which feed to pick.

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

Usage Guidelines3/5

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

The only explicit guidance is incremental polling: use `after` with the returned cursor to fetch newer messages. There is no statement of when to prefer this over read_room or read_inbox, nor any exclusion, so usage is implied rather than directed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources