Skip to main content
Glama
Sign In
Andon SOP MCP Server

Andon SOP MCP Server

by guansuian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

auditProductionTask

Batch audit and release production tasks. Only tasks with checkStatus 0 (not released) are allowed; must query task list first.

Instructions

批量下达生产任务，调用 /productionTask/audit。调用本工具前必须先调用 queryProductionTaskList 查询生产任务并让用户选择要下达的任务。只有 checkStatus 为 0（未下达）的生产任务允许下达；其他状态不能下达。本工具会在下达前校验每个生产任务的 checkStatus。

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": {
      "tasks": "<tasks>"
    },
    "name": "auditProductionTask"
  }
}

Input Schema

NameRequiredDescriptionDefault
tasksYes要下达的生产任务列表。必须来自 queryProductionTaskList 查询结果，支持批量下达。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided. The description covers validation behavior (checking checkStatus before release) and preconditions. However, it does not disclose error handling (e.g., partial failures, atomicity) or side effects beyond validation.

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?

Concise and well-structured: purpose first, then prerequisites, then constraints. Each sentence adds value without repetition.

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?

Lacks details about the return value or output, especially since there is no output schema. The description covers preconditions and validation but does not explain what the tool returns (e.g., success/failure details).

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 coverage is 100%, with detailed field descriptions. The description reinforces that tasks must come from queryProductionTaskList and checkStatus must be 0, but these are already implicit in the schema. No new semantic constraints beyond schema.

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 clearly states the tool's purpose: '批量下达生产任务' (batch release production tasks) and specifies the API endpoint. It also distinguishes itself from siblings like reverseAuditProductionTask, which likely reverts releases.

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

Usage Guidelines5/5

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

Explicitly states that queryProductionTaskList must be called first, tasks must be selected by the user, and only tasks with checkStatus=0 are allowed. This provides clear when-to-use and when-not-to-use guidance.

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