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

mrt-fe-review-washer

by jaeuk-mrt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

task.execute

Initiates task execution, sets status to in_progress, and provides an execution guide. Start tasks with clear, step-by-step instructions.

Instructions

Task 실행을 시작합니다. 상태를 in_progress로 변경하고 실행 가이드를 제공합니다.

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

Input Schema

NameRequiredDescriptionDefault
idYesTask ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The description discloses two behavioral traits: changing status to 'in_progress' and providing an execution guide. However, with no annotations, it fails to mention preconditions, reversibility, or what happens if the task is already in_progress, partially meeting the transparency burden.

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?

Two short, front-loaded sentences with no filler. Each sentence adds meaningful information: starting execution and the status change plus guide provision.

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

Completeness3/5

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

For a one-parameter tool with no output schema, the description gives the core action but leaves ambiguity about what the 'execution guide' contains, any prerequisites, and how it relates to sibling tools like task.complete or task.verify. It is adequate for basic invocation but not fully complete.

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?

The only parameter 'id' has a complete schema description ('Task ID'), with 100% coverage. The description adds no additional meaning about the parameter, so the baseline score of 3 applies.

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?

The description uses a specific verb '실행을 시작합니다' (starts execution) and clearly identifies the resource as Task. It also states two concrete actions: changing status to 'in_progress' and providing an execution guide, which distinguishes it from siblings like task.complete or task.update_status.

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

Usage Guidelines3/5

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

The description implies usage for starting task execution but provides no explicit when-to-use guidance or alternatives. It does not reference sibling tools or state when not to use, leaving the usage context implied rather than explicit.

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