Skip to main content
Glama

Aufgabe kommentieren

comment_task

Schreibt einen Kommentar auf eine Karte (wie bei Trello) – z. B. die Antwort auf eine @Claude-Erwähnung. Erscheint in der Glocke der Lehrkraft. Ohne text: liefert Kommentare und Aktivität der Karte (neueste zuerst).

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": {
      "task_id": "<task_id>"
    },
    "name": "comment_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The description adds useful behavioral context beyond the annotations: the comment appears in the teacher's notification bell, and omitting text switches to a read operation returning newest-first. Annotations already establish a non-read-only, non-destructive tool, and the description fills in the side effect and dual-mode behavior.

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 compact sentences with no filler, front-loading the write behavior before the read fallback and the notification side effect. Every sentence contributes useful information.

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 output schema, the description still explains that read mode returns comments and activity newest-first, which is helpful. It is nearly complete for a simple dual-mode comment tool, though it does not describe the write-mode return value.

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 0%, so the description must carry parameter meaning. It explains the semantics of text thoroughly, including the omitted-text read mode, but task_id is only implied by 'Karte' and is not explicitly defined as the target card identifier.

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 description names a specific verb and resource: writing a comment on a card, with a Trello-like analogy. It also discloses the read-mode behavior when text is omitted, but it does not explicitly contrast this tool with any sibling tool.

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 a concrete usage example (replying to an @Claude mention) and clearly states the condition for read mode: omit text to retrieve comments and activity. It does not mention when not to use the tool or name alternatives, but the mode-selection guidance is clear.

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