Skip to main content
Glama

Tick the steps you did

tick

Tick steps you did yourself, as you finish each. All or nothing: one unknown text ticks none; a text two steps share ticks the next open one. On the person's own tasks it reports the step done, for them to confirm.

Instructions

Tick steps you did yourself, as you finish each. All or nothing: one unknown text ticks none; a text two steps share ticks the next open one. On the person's own tasks it reports the step done, for them to confirm. Refused once the task is said done: note instead. The whole task is say_done; a wrong tick, untick.

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": "<task>"
    },
    "name": "tick"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepNoOne step, by its text
taskYesThe task id
stepsNoThe steps you did, by their text as `read` shows it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.47.1
    • changedInput schema / properties / steps / description
      Previous value: -"The steps you did, by their text as `read` shows it; case and accents do not matter"New value: +"The steps you did, by their text as `read` shows it"
  2. Changed2 schema fields changedv1.43.2
    • changedInput schema / properties / step / description
      Previous value: -"One step, by its text — the same as `steps` with one entry"New value: +"One step, by its text"
    • changedInput schema / properties / steps / description
      Previous value: -"The steps you did, each by its text as `read` shows it — capitals, accents and the spaces at either end decide nothing. One of `steps` or `step` has to come with the call"New value: +"The steps you did, by their text as `read` shows it; case and accents do not matter"
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: all-or-nothing matching ("one unknown text ticks none"), ambiguity resolution ("a text two steps share ticks the next open one"), a refusal state after task completion, and the confirmation flow on someone's own tasks. It does not cover permission scope or what happens when ticking a task that is not the person's own, which the sentence about "the person's own tasks" hints at but leaves unexplained.

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?

Front-loaded with the action, then the rules, then the sibling routing — a logical order with no filler. Some clauses are telegraphic to the point of needing a re-read ("a text two steps share ticks the next open one").

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 and a mutation annotation profile, the description supplies the missing pieces: matching rules, refusal condition, and the observable outcome (the step is reported done for the user to confirm). The gap is the distinction between the person's own tasks and other tasks, whose differing behavior is implied but never stated.

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 100%, so each parameter is already documented; the description's added value is behavioral (atomicity of `steps`, matching by text) rather than per-parameter syntax or format. It does not clarify when to pass singular `step` versus the `steps` array, which is the main ambiguity an agent would face.

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?

Specific verb+resource ("Tick steps you did yourself, as you finish each") with scope stated (your own steps, incremental). It explicitly marks the boundaries against the whole-task operation ("The whole task is `say_done`") and the correction path ("a wrong tick, `untick`").

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?

Gives the trigger ("as you finish each"), the prohibition ("Refused once the task is said done"), and the replacement tool for that case (`note`). It also routes two other cases to named siblings: `say_done` for the whole task and `untick` for mistakes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.