Skip to main content
Glama

comment_on_post

Leave a comment on a post the user is reviewing, wrote, or can see as an admin. It decides and blocks nothing: for a verdict use approve_post or send_back_post. Use for feedback, a question, or a note. The text is stored verbatim, so pass the user's own words. The author and the other reviewers are notified. Ids come from list_posts_awaiting_my_review or list_drafts.

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": {
      "post_id": "<post_id>",
      "comment": "<comment>"
    },
    "name": "comment_on_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentYesThe comment, in the user's own words
post_idYesThe id of the post to comment on
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses real side effects: the text is stored verbatim, and the author plus other reviewers are notified. It also clarifies the authority boundary — commenting does not alter post state — which the annotations alone cannot express.

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?

Four short sentences, front-loaded with purpose, then the negative boundary, then the storage/notification behavior, then id provenance. There is no filler and nothing that duplicates structured fields verbatim.

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 simple three-parameter write tool with no output schema, the description covers purpose, boundaries, side effects, and id sourcing. It does not say what is returned (whether the created comment id or object comes back), which an agent doing follow-up work would want, but otherwise it is complete.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: post_id provenance (which list tools produce valid ids) and the verbatim-storage constraint on the comment text. The optional workspace parameter is left entirely to its schema entry, which is a minor remaining gap.

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 opens with a specific verb and resource ("Leave a comment on a post") and immediately bounds the scope to posts the user is reviewing, authored, or can see as an admin. It explicitly contrasts itself with the verdict tools (approve_post, send_back_post), so an agent can place it among siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states both when to use it ("feedback, a question, or a note") and when not to ("It decides and blocks nothing: for a verdict use approve_post or send_back_post"), naming the exact alternatives. It also tells the agent where valid post ids come from (list_posts_awaiting_my_review or list_drafts), removing the most likely invocation error.

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.

Resources