Skip to main content
Glama

CarlNotes

Follow a topic

follow_topic
Idempotent

Follow a CarlNotes topic for the connected account, or unfollow it. Following puts the topic in the account's feed and its list. An owner always follows their own topic. Use it when the user asks Carl or CarlNotes to follow a topic, with phrases like follow this topic or unfollow this topic.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "is_following": "<is_following>"
    },
    "name": "follow_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
topic_idNoThe topic's id. Optional on a topic-bound server, which already knows its topic.
is_followingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, and the description adds real context beyond them: following places the topic in the feed and list, and an owner always follows their own topic — an invariant an agent would otherwise miss. It does not say what actually happens if an agent passes is_following=false for a topic the account owns (error vs. no-op), leaving the key edge case implied.

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, front-loaded with the action, followed by the behavioral effect and then the invocation trigger. Every sentence carries distinct information and nothing is repeated from the title or schema.

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 write tool with no output schema, the description covers purpose, side effects, the owner-follow invariant, and the calling context, which is close to sufficient. The remaining gap is outcome reporting — whether the call returns the resulting follow state or errors on an invalid unfollow — which matters slightly more given there is no output schema.

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 50%: topic_id is documented in the schema, but is_following has no schema description. The description conveys the toggle semantics through "follow ... or unfollow it," which maps the boolean meaning, but it adds no detail on defaults, error conditions, or how topic_id resolution behaves off a topic-bound server beyond what the schema already says.

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?

States a specific verb and resource ("Follow a CarlNotes topic for the connected account, or unfollow it") and names the boolean-toggle dual behavior up front. It also makes clear the effect (topic appears in the account's feed and list). It does not explicitly distinguish itself from sibling write tools like edit_topic or create_topic, so it stops short of a 5.

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 an explicit usage trigger: "Use it when the user asks Carl or CarlNotes to follow a topic, with phrases like follow this topic or unfollow this topic." That is concrete routing guidance including natural-language cues. It offers no when-not conditions or named alternatives for related operations (e.g., creating vs. following a topic), which keeps it below a 5.

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.