Skip to main content
Glama
Sign In
mrt-fe-review-washer

mrt-fe-review-washer

by jaeuk-mrt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

task.update_status

Update a task's status to pending, in_progress, completed, or cancelled using its ID. Streamline review workflow by tracking task progress.

Instructions

Task 상태를 변경합니다.

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": {
      "id": "<id>",
      "status": "<status>"
    },
    "name": "task.update_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTask ID
statusYes변경할 상태

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies mutation ('변경') but doesn't disclose permissions, reversibility, validation rules, or side effects. The schema's enum gives statuses but no transition constraints.

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?

A single sentence with no wasted words. The description is front-loaded with the core action and is appropriately sized for a simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description should provide more behavioral and side-effect context. It only states the basic action, omitting when to use it, return behavior, or potential implications, making it incomplete for a mutation tool.

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%, with clear descriptions for both 'id' and 'status'. The tool description adds no additional parameter context, so the baseline of 3 is appropriate.

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 clearly states the tool changes task status ('Task 상태를 변경합니다'), using a specific verb and resource. However, it doesn't distinguish from sibling tools like task.complete, which may also modify status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as task.complete or task.verify. The description only states the action, leaving the agent to infer usage.

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