Skip to main content
Glama

CarlNotes

React

save_reaction
Idempotent

Leave the connected account's reaction on a CarlNotes finding, podcast episode, topic, Open Mic post, or hot take: one of six positive types. A reaction is public wherever its topic is, and each account has one per thing it reacts to. A new save changes the type, and a save with no type removes it. Use it when the user tells Carl to react to this or like this finding.

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": {
      "target_kind": "<target_kind>",
      "target_id": "<target_id>"
    },
    "name": "save_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_idYesThe id of the finding, the podcast episode, the topic, the topic post, or the hot take.
target_kindYesWhat it is on: a finding, a podcastEpisode, a topic, a post, which is a topic's Open Mic post, or a comment, which is a hot take.
reaction_typeNoThe reaction type, or null to remove it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), it discloses that reactions are public wherever the topic is, that each account has exactly one reaction per target, that a new save overwrites the type, and that a save with null removes the reaction. These facts explain the uniqueness/overwrite model that the idempotentHint only hints at, and the null-removal behavior is a meaningful behavioral trait for a write tool.

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 tight sentences, each doing distinct work: scope first, then the behavioral model (public, one-per-account, overwrite/remove), then the usage trigger. No filler, no repetition of the title, and the most important scoping information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter write tool with no output schema and partial annotation coverage, the description supplies the missing pieces: visibility of the effect, cardinality, overwrite and removal semantics, and the trigger condition. Nothing an agent would need in order to call this correctly appears absent.

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 description coverage is 100%, so the schema already documents target_id, target_kind, and reaction_type in full, including the null-to-remove semantics and the post/comment to Open Mic post/hot take mapping. The description largely restates those mappings in friendlier prose; "one of six positive types" adds a small amount of framing but no syntax or constraint detail beyond the schema. Baseline 3 applies.

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 ("Leave the connected account's reaction on a CarlNotes finding, podcast episode, topic, Open Mic post, or hot take") and enumerates the exact target kinds, so the agent knows precisely what the tool operates on. It never names a sibling such as rate_finding or bookmark_finding, so the boundary with adjacent tools is left implicit rather than stated.

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?

"Use it when the user tells Carl to react to this or like this finding" gives a clear triggering condition and even suggests the natural user phrasing to match against. There is no explicit when-not guidance and no alternative tool named for cases where the user wants to bookmark, rate, or report instead, which keeps it short of 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.