Skip to main content
Glama

CarlNotes

Read a topic's feed

read_topic_feed
Read-only

A CarlNotes topic's findings in relevance order, each with Carl's relevance explanation. A connected account's read includes which findings it read and bookmarked. Use it when the user asks Carl or CarlNotes for a topic's findings, with phrases like show this topic, what did Carl find, or read my feed.

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

Input Schema

NameRequiredDescriptionDefault
cursorNoThe cursor a previous page returned.
topic_idNoThe topic's id. Optional on a topic-bound server, which already knows its topic.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description goes beyond that by disclosing the return shape: findings in relevance order with per-finding relevance explanations, plus per-account read and bookmark state for connected accounts. It stops short of describing pagination behavior or what happens with an empty feed, which matters since no output schema exists.

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?

Two sentences, front-loaded with what the tool returns before the usage triggers. The trailing list of example phrases is slightly chatty but earns its place as selection guidance.

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?

For a two-parameter, read-only, no-output-schema tool, the description covers content shape, per-account state, and invocation triggers — enough to call it correctly. Remaining gaps (pagination semantics, ordering ties, empty-feed behavior) are modest given the schema handles the parameters.

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 the cursor and the optional topic_id (including the topic-bound-server case) are already fully documented in the schema. The description adds nothing about either parameter, so it meets the baseline without adding value.

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?

The description names a specific resource — a CarlNotes topic's findings, ordered by relevance, each carrying Carl's relevance explanation — so the agent knows exactly what is returned. It doesn't explicitly distinguish itself from lookalike siblings such as search_topic_findings or read_topic_posts, leaving the feed-vs-search-vs-post distinction to inference.

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 trigger conditions: use when the user asks Carl or CarlNotes for a topic's findings, with example phrasings like 'show this topic', 'what did Carl find', or 'read my feed'. That is strong positive guidance, but it names no exclusions or alternative tools, so an agent must still guess what to call instead when the user wants search or a single post.

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.