Skip to main content
Glama
Sign In
Legion Workflow MCP

Legion Workflow MCP

by mmm906433
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

brigade_template

Provides usage guidance and parameter templates for legion workflow, explaining when to invoke a parallel subagent run and how to poll its status correctly.

Instructions

军团工作流的使用说明与参数模板（什么时候该用 / 怎么轮询）。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "brigade_template"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It hints at behavior by mentioning polling ('怎么轮询'), which is useful context for an agent coordinating the workflow, but it never states that this is a read-only informational resource or what happens on invocation. Modest but incomplete disclosure.

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 short sentence with the resource front-loaded and the two key topics (when to use, how to poll) bracketed at the end. No waste, nothing padded.

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 zero-parameter guide tool with no output schema, the description should at least characterize the shape of what comes back (template fields, polling cadence). It gestures at the content but leaves the return format entirely undefined, which is a real gap for a tool whose whole value is its payload.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The 'parameter template' phrasing refers to the tool's content, not to inputs, so no parameter semantics are actually required.

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 names a specific resource — usage instructions and a parameter template for the brigade workflow — which is distinct from the run/status/list/stop siblings. However it states the resource as a noun phrase with no verb and never explicitly says 'call this to get X', so sibling differentiation is implied rather than stated.

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?

It claims to contain 'when to use' guidance (什么时候该用), which implies the tool is a routing aid, but the description itself does not tell the agent when to invoke this tool versus brigade_run or brigade_status. Usage is left to be discovered from the tool's payload rather than stated in the definition.

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