Skip to main content
Glama
Sign In
@contextq/mcp

@contextq/mcp

Official
by contextq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

agent_task_tick

Update a session checklist item's status as work is proven, requiring real evidence to mark it verified. Use when a user reports finishing tracked work.

Instructions

Flip a task's status. Setting status='verified' REQUIRES non-empty evidence (real observed output: test result, HTTP status, exit code) — the no-self-certification rule. Returns 400 if you try to verify without evidence. Use this as each checklist item is proven. Trigger: user reports finishing a piece of tracked work ("xong rồi", "xong X", "done X", "done", "mark done", "finished X") — tick the matching session-scoped checklist item here (use goal_advance instead for a board-level task). Only call when it maps to a tracked item; ignore unrelated casual chatter.

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>",
      "status": "<status>"
    },
    "name": "agent_task_tick"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesNew status
task_idYesTask id to tick
evidenceNoReal observed output proving the task (required to set 'verified')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does so well: it discloses the no-self-certification rule, that status='verified' requires non-empty evidence, and the 400 failure mode. It stops short of stating reversibility, idempotency, or what a successful call returns, which are the remaining gaps.

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 core action and the hard constraint, then the trigger guidance. Dense but every clause carries information; the parenthetical phrase list is slightly verbose but serves a routing purpose.

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 3-param mutation tool with no annotations and no output schema, the definition supplies the conditional requirement, the error behavior, the routing trigger, and the sibling alternative. Only the success response shape and state-transition semantics are left unstated, which is a minor gap.

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 is 3, but the description adds real meaning: it ties the `evidence` parameter to a specific semantic requirement (real observed output such as test result, HTTP status, exit code) and couples it conditionally to status='verified'. That is meaningfully beyond the bare schema text.

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?

States a specific verb+resource ('Flip a task's status') and immediately distinguishes itself from the sibling goal_advance, which handles board-level tasks. An agent can tell exactly what this does and what it is not.

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?

Explicit trigger conditions are given ('user reports finishing a piece of tracked work' with concrete phrases), an exclusion is stated ('ignore unrelated casual chatter'), and the alternative tool is named for the board-level case. This is close to ideal routing guidance.

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

Deploy Server

Other Tools