Skip to main content
Glama

CarlNotes

List topics

list_topics
Read-only

The topics you may read on CarlNotes, Carl's app: the public ones for everyone, plus what a connected account owns, follows, and holds through a team. A section lists one section of the topics page: yours, followed, featured, or popular. similar_to_topic_id lists the similar topics a topic's page shows. Use it when the user asks Carl or CarlNotes for topics, with phrases like list my topics, what topics do I follow, what is popular, topics like this one, or what does Carl cover.

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

Input Schema

NameRequiredDescriptionDefault
cursorNoThe cursor a previous page returned.
sectionNoOne section of the topics page. A visitor reads featured and popular.
similar_to_topic_idNoA topic whose similar topics to list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations declare only readOnlyHint=true, so the description must fill in the rest, and it does by disclosing the visibility model (public topics versus the connected account's own, followed, and team-held topics) and the meaning of a 'section'. It omits any statement about pagination or ordering, which it leaves entirely to the cursor parameter's schema text.

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?

It is a single dense paragraph that front-loads what the tool returns, then explains the two filtering parameters, then ends with usage triggers. The example phrases are long but they are functional; only minor tightening is possible.

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?

This is a read-only tool with three parameters, all documented, and no output schema, so the description only needs to explain visibility and how to select a view, and it does both. The only gap is pagination and ordering behavior when no section is supplied.

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 the schema already documents all three parameters and establishes the baseline of 3. The description reinforces the section options and explains that similar_to_topic_id yields the topics a topic's page shows, which clarifies intent but adds little beyond the existing schema descriptions, and cursor receives no mention 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?

The description pairs a specific verb and resource ('The topics you may read on CarlNotes') with an explicit scope: public topics plus what a connected account owns, follows, or holds through a team. That framing lets an agent distinguish it from create_topic, suggest_topics, and read_topic_feed without opening any 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 names concrete trigger phrases ('list my topics', 'what topics do I follow', 'what is popular', 'topics like this one') that map to real invocation contexts. It stops short of naming alternatives or exclusions, so an agent must infer on its own that read_topic_feed or suggest_topics covers other needs.

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.