Skip to main content
Glama

CarlNotes

Add a hot take

post_hot_take

Post the connected account's hot take on a CarlNotes finding, podcast episode, topic, or Open Mic post, or a reply to one: plain text of up to 2000 characters, where @username mentions someone. A hot take is public wherever its topic is. On a podcast episode it may name a chapter by its position. Use it when the user tells Carl to leave a hot take, post a comment, or reply to the conversation.

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>",
      "body": "<body>"
    },
    "name": "post_hot_take"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe hot take's text.
parent_idNoThe id of the hot take this one replies to, if it is a reply.
target_idYesThe id of the finding, the podcast episode, the topic, or the topic post.
target_kindYesWhat it is on: a finding, a podcastEpisode, a topic, or a post, which is a topic's Open Mic post.
chapter_positionNoThe position of the podcast episode's chapter the hot take is about, from 0 for the first.

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?

Annotations already declare non-read-only, non-idempotent, and non-destructive behavior. The description adds useful behavioral context that the annotations do not: hot takes are public wherever their topic is, and @username mentions someone. It does not cover authentication or rate limits.

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 description is a single front-loaded paragraph that covers purpose, target types, public visibility, chapter handling, and usage guidance. It is slightly run-on but each sentence carries relevant context.

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 public posting mutation with five parameters and full schema coverage, the description covers the essential purpose, targets, visibility, mention syntax, and usage conditions. It omits auth and return-value details, but no output schema exists and annotations already carry the safety profile.

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 defines all five parameters. The description adds @mention semantics and chapter-position context, but it also states a 2000-character body limit while the schema sets maxLength to 20000, which is a notable inconsistency.

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 states a specific verb and resource: posting the connected account's hot take on a finding, podcast episode, topic, Open Mic post, or reply. It clearly distinguishes the action from read/delete hot take siblings through explicit scope and target types.

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 explicitly says to use this when the user tells Carl to leave a hot take, post a comment, or reply to the conversation. It does not name alternatives such as delete_hot_take or read_hot_takes, nor does it state when not to use it.

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.