Skip to main content
Glama

Take back a tick given by mistake

untick

Take back a tick, or your word on a step, an agent gave by mistake. A tick the person gave is theirs, and naming it unticks nothing. It opens and closes nothing.

Instructions

Take back a tick, or your word on a step, an agent gave by mistake. A tick the person gave is theirs, and naming it unticks nothing. It opens and closes nothing.

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

Input Schema

NameRequiredDescriptionDefault
stepNoOne step, by its text
taskYesThe task id
stepsNoThe steps to untick, 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 to untick, by their text as `read` shows it; case and accents do not matter"New value: +"The steps to untick, 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 to untick, 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 to untick, by their text as `read` shows it; case and accents do not matter"
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, the description adds the important ownership constraint that person-given ticks cannot be unticked and clarifies that the operation opens or closes nothing. It still does not spell out idempotency or return behavior, but with annotations covering safety and world scope this is useful added context.

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?

The action is front-loaded and the description is short, with the key exclusion in the second sentence. The phrasing 'or your word on a step' and 'It opens and closes nothing' is somewhat cryptic, which keeps it from being maximally crisp.

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 three-parameter mutation with no output schema and annotations covering safety, the description supplies the main non-obvious constraints an agent needs. It leaves some minor details implicit but is complete enough to call correctly.

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%, so task, step, and steps are already documented. The description's references to 'a step' and 'naming it' do not add syntax or selection guidance beyond the schema, so the baseline 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 names a specific inverse action ('Take back a tick') on a step and scopes it to ticks an agent gave by mistake. That makes the action and resource clear, though it does not explicitly name the 'tick' sibling as the alternative.

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 clear when-to-use guidance: undo an agent-given tick given by mistake. It also gives a when-not condition by saying a person-given tick belongs to the person and naming it unticks nothing, but it does not explicitly point to the tick tool for the opposite action.

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