Skip to main content
Glama

CarlNotes

Post in a team chat

post_to_team_room

Post a message to a CarlNotes team's chat as a member, optionally as a reply to one of its messages. A message that names Carl gets his reply in the chat. Use it when the user asks Carl or CarlNotes to post in the team chat, tell my team, or reply in the team chat.

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": {
      "team_id": "<team_id>",
      "message": "<message>"
    },
    "name": "post_to_team_room"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYes
team_idYesThe team's id, from list_teams or read_team.
reply_to_chat_message_idNoA message id from read_team to reply to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the write/non-idempotent profile is known. The description adds genuinely new behavior: posting happens 'as a member' (an auth/identity constraint) and 'A message that names Carl gets his reply in the chat' (an automatic side effect the caller would not otherwise expect). It omits other behavioral facts such as the 4000-character cap's practical implication, rate limits, or what happens on duplicate posts.

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 short sentences, front-loaded with what the tool does, then the Carl-reply side effect, then the trigger conditions. No filler or restatement of the tool name.

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 3-parameter write tool with no output schema and useful annotations, this covers purpose, threading, identity requirement, and invocation triggers. It would be stronger if it stated what a successful call returns (e.g. the created message id, needed for a follow-up reply) or noted length constraints on the body.

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 67%: team_id and reply_to_chat_message_id are already documented, and message's length bounds are in the schema. The description adds real meaning for message by explaining that naming Carl in the body triggers an automated reply, and the 'optionally as a reply' phrase clarifies the optional parameter's role. Marginal but useful above the schema baseline.

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?

The opening clause gives a precise verb and resource ('Post a message to a CarlNotes team's chat') plus an optional mode ('as a reply to one of its messages'). It is clearly distinct from read/fetch siblings, but it never names or contrasts with plausible alternatives like send_to_topic or post_hot_take, leaving the agent to infer the boundary between 'team chat' and 'topic' surfaces.

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?

The final sentence gives concrete trigger phrases ('asks Carl or CarlNotes to post in the team chat', 'tell my team', 'reply in the team chat'), which is strong when-to-use guidance. It stops short of any when-not guidance, e.g. that unrelated topic-thread posting belongs to a different tool.

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.