Skip to main content
Glama

CarlNotes

Read your activity

read_activity
Read-only

The connected account's CarlNotes activity: the topics they own with this month's scans and cost, the topics they follow, the topic and team invites waiting for their answer, each with the invite id respond_to_invite takes, and the invites they sent. Names are people's words, returned as data. Use it when the user asks Carl or CarlNotes for my activity, my invites, or what topics do I follow.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish the safe read profile (readOnlyHint true, destructiveHint false), and the description adds real context: this is a multi-section aggregate, and names are contributor-supplied data ('people's words, returned as data'), a useful handling caveat. It also explains that invite ids returned here are the inputs respond_to_invite expects, which is behavior annotations cannot convey.

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?

The payload is front-loaded in the first sentence, followed by a short usage trigger sentence; every clause maps to a returned section or a routing cue. The single long enumeration sentence is dense but not padded, though it could be split for faster scanning.

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 parameters and no output schema, the description carries the return-shape burden and does so by enumerating each section returned. Ordering, pagination, and cost formatting are unstated, but for a zero-parameter aggregate read the definition is sufficient to call it correctly.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. No parameter meaning needs to be conveyed, and the description correctly adds no parameter noise.

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 names the exact resource and enumerates its parts: topics the account owns with this month's scans and cost, followed topics, pending topic and team invites (with the invite id), and sent invites. This is a specific aggregate-read and is clearly distinguishable from siblings like read_dashboard or read_profile.

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 phrasing ('my activity', 'my invites', 'what topics do I follow') and points to the sibling that consumes the invite id, respond_to_invite. It does not state explicit exclusions (e.g., use read_topic_feed for topic content), so it falls just short of a full when/when-not/alternatives statement.

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.