Skip to main content
Glama

Say a task should not be done

say_not_doing
Idempotent

Records that a task should not be done and explains why it became moot, without dropping it—the person decides; later news goes in the note.

Instructions

Say a task should not be done, on any task, as your word: it stopped mattering or became moot. Unticked steps do not stop it. Nothing drops: the person decides. Say it once; news after goes in note.

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>",
      "body": "<body>"
    },
    "name": "say_not_doing"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesWhy it should not be done, and what you found that says so, in the Tisty language
taskYesThe task id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.43.2
    • changedInput schema / properties / body / description
      Previous value: -"The account the person reads before deciding: why it should not be done, and what you found that says so. In the Tisty language"New value: +"Why it should not be done, and what you found that says so, in the Tisty language"
    • changedInput schema / properties / task / description
      Previous value: -"The task's id, as `find` or `propose` gave it"New value: +"The task id"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Adds meaningful behavior beyond the annotations: the task is not removed or dropped, the human retains the decision, unticked steps do not prevent the declaration, and it should be said once (reinforcing idempotentHint=true). This is genuinely useful context for a write operation with destructiveHint=false. It stops short of describing any response or notification effect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded with the action, but the middle clause is dense and slightly ungrammatical ("on any task, as your word: it stopped mattering or became moot"), which slows comprehension. No wasted sentences, but clarity is traded for terseness.

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 two-parameter declaration tool with annotations covering the safety profile and no output schema, the description covers what it does, how it interacts with steps, what it does not do (drop the task), and where follow-up information goes. Nothing essential to correct invocation appears missing.

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 would be 3, but the description adds a real constraint on `body`: it carries the reason and supporting evidence, while subsequent news belongs in `note`. That distinction is not derivable from the schema alone and directly shapes what the agent writes.

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?

States a concrete verb+resource: declaring that a task should not be done, applicable to "any task". It also implicitly distinguishes itself from say_done and explicitly routes follow-up content to the `note` sibling. The phrasing "as your word: it stopped mattering or became moot" is a bit compressed, but the core action is unambiguous.

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?

Gives real usage context: it applies to any task, unticked steps do not block it, and the declaration is advisory rather than decisive ("Nothing drops: the person decides"). It also sets a when-not boundary by sending later news to `note` instead of repeating this call. No explicit list of alternatives beyond `note`, but the guidance is clear.

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