Skip to main content
Glama

CarlNotes

Read Brews News

read_news
Read-only

Read the connected account's CarlNotes Brews News: who mentioned them in a hot take, then what happened on their own topics, their teams' topics, and the topics they follow, over the last week, day, or hour: new podcast episodes, Open Mic posts, hot takes, reactions, and findings. It marks nothing as read or seen. Use it when the user asks Carl for Brews News, what happened this week, or who mentioned me.

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_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoThe cursor a previous page returned.
windowNoHow far back to read: week, day, or hour. Leave it out for week.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description adds genuinely useful context beyond that: 'It marks nothing as read or seen' and the explicit ordering (mentions first, then own topics, teams' topics, followed topics). However, it says nothing about pagination behavior despite a cursor parameter, or about result volume/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?

Front-loaded with the purpose and scope, and the trigger sentence closes it out cleanly. The middle content listing is a long, comma-heavy run that could be tightened, but every clause carries real information about what the feed returns.

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?

With no output schema, the description usefully enumerates the item types returned, which is the main thing an agent needs to trust the result shape. It is slightly incomplete on paging ('cursor a previous page') and on how many items a window returns, but nothing critical is missing for a two-optional-parameter read tool.

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 100%, so both parameters are fully documented structurally. The description restates the window values (week, day, hour) and the default, but adds no meaning beyond the schema's own enum descriptions, and the cursor is not mentioned at all.

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 ('Read the connected account's CarlNotes Brews News') and enumerates exactly what the feed contains: mentions in hot takes first, then own/team/followed topics, with item types (podcast episodes, Open Mic posts, hot takes, reactions, findings). This is distinguishable from narrower siblings like read_hot_takes or read_updates.

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 concrete invocation triggers: 'when the user asks Carl for Brews News, what happened this week, or who mentioned me.' Clear context for use, but it names no exclusions or alternatives among the many read_* siblings, so an agent must infer that this is the aggregated view rather than a per-entity reader.

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.