Skip to main content
Glama
Sign In
SummitFlow MCP

SummitFlow MCP

by zrzqbr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

执行质量门禁

summit_run_quality_gate
Idempotent

Run predefined quality gates for code changes, executing type checks, MCP tests, and application tests to validate repository health before deployment.

Instructions

只执行仓库内固定的类型检查、MCP测试和应用测试命令；不接受任意Shell命令。

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": "summit_run_quality_gate"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoquick

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already convey idempotence and non-destructiveness. The description adds meaningful behavioral context by stating that only fixed commands are executed and arbitrary Shell input is rejected, which is important safety-relevant information beyond the annotations.

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?

The description is one tightly worded sentence with two clauses. The scope is front-loaded and the safety boundary is stated directly after, with no filler or repetition.

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 simple tool with one optional enum parameter and safety annotations, the description is mostly complete: it specifies which command categories run and explicitly rejects arbitrary input. The remaining gap is the lack of profile semantics and expected output behavior, but this is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter, profile, is not mentioned in the description at all, and schema description coverage is 0%. The enum values quick/full are self-descriptive, but the description does not explain what each profile includes or how it changes the run.

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 states a specific verb and resource: it executes only the repository's fixed type-check, MCP test, and application test commands. It also explicitly excludes arbitrary Shell commands, which clearly distinguishes it from generic command-execution tools.

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 the tool is for running the repository's predefined quality gates, but it does not say when to prefer it over alternatives or mention sibling tools. It provides a constraint rather than active usage guidance or explicit exclusions.

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