Skip to main content
Glama
Sign In
shipfast-mcp

shipfast-mcp

by QuocTang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Open Wave

open_wave

Create a new wave by generating its docs/04_waves folder from the project template and adding an Intake row to the wave table, so teams can start tracking planned work.

Instructions

Mở wave mới: tạo docs/04_waves/Wxx/ từ mẫu của dự án, thêm dòng vào bảng wave ở trạng thái Intake.

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": {
      "project_dir": "<project_dir>",
      "title": "<title>",
      "goal": "<goal>"
    },
    "name": "open_wave"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesMột câu: sau wave này người dùng hoặc PO có được gì
leadNoChủ trì: Orchestrator hoặc mã bộ phậnOrchestrator
modeNopo: PO chốt từng vấn đề. direct: chốt thẳng cho wave nhỏ. delegated: delegation, cần QT-nnnpo
titleYesTên wave
project_dirYesĐường dẫn tuyệt đối tới gốc repo dự án

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds real substance beyond that by naming the two side effects (template directory creation and wave-table row insertion) and the resulting status. It stops short of covering idempotency (what happens if the Wxx directory already exists) or what the 'mode' choice changes operationally.

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 front-loaded sentence that leads with the action and then enumerates the concrete artifacts produced. No filler, no restatement of the title.

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

Completeness5/5

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

With annotations covering the safety profile, a fully described schema, and an output schema to carry return values, the description supplies exactly what is missing: the concrete filesystem and table side effects. Nothing an agent needs to invoke it correctly is absent.

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 every parameter including the mode enum and lead default is already documented in the schema. The description adds no parameter-level meaning beyond that, which is the correct baseline of 3 when the schema carries the load.

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 states a specific verb and resource ('Mở wave mới') and backs it with concrete effects: creating docs/04_waves/Wxx/ from the project template and appending a row to the wave table at status Intake. It does not name a sibling it could be confused with (e.g. scaffold_project), so differentiation is left implicit.

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?

Usage is only implied by the described effect and the 'Intake' status — an agent can infer this is the entry point for starting a new wave. There is no explicit when-to-use/when-not statement, no prerequisites, and no mention of an alternative path for creating waves.

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