Skip to main content
Glama

Check a task (done)

check_task
Idempotent

Mark an armed task as done: it is unarmed and its ticker goes up by 1. On a task that is not armed it changes nothing (compare ticker before and after).

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": "check_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesThe task's id (from list_tasks, todays_tasks or a loop's tasks).

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?

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true), the description discloses the actual side effects: the task is unarmed and a ticker counter increases by one, and on an unarmed task nothing happens, which is consistent with idempotentHint. The 'compare ticker before and after' note usefully explains how to distinguish a real change from a no-op. It does not cover error behavior for an invalid task_id or what is returned, so it falls short of a 5.

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?

Two sentences, front-loaded with the primary effect and followed by the exception case. Every clause carries information: the effect, the arm-state precondition, the no-op behavior, and the verification hint.

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 compensates by telling the agent how to verify the outcome via the ticker. For a single-parameter mutation with safety annotations already present, nothing essential is missing beyond error/return semantics for an invalid or nonexistent task_id.

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% and the single task_id parameter is already documented with its sources (list_tasks, todays_tasks, loop tasks). The description adds no further meaning about the parameter itself, so the baseline of 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?

The description states a concrete verb and effect on a specific resource: an armed task becomes done, is unarmed, and its ticker increments by 1. That is far more informative than the ambiguous name 'check_task', which could be mistaken for a read operation. It stops short of naming a sibling (e.g. enqueue_task or arm_all) to contrast with, so it is clear but not sibling-differentiated.

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 an explicit precondition (the task must be armed) and an explicit no-op case (an unarmed task changes nothing), plus a way to detect the no-op. What is missing is routing guidance: it never says how to arm a task first or which sibling to use for the read-only inspection case.

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