Skip to main content
Glama
Sign In
Andon SOP MCP Server

Andon SOP MCP Server

by guansuian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

saveCategory

Add a SOP category. If a parent category ID is provided, the new category will be placed under it; otherwise, it becomes a root category.

Instructions

新增 SOP 分类。调用前应先使用 selectCategoryTreeList 查询分类树，让用户选择父分类；将选择数据中的 id 作为 parentId。未传 parentId 时默认创建到 ROOT。

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": {
      "title": "<title>"
    },
    "name": "saveCategory"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes新分类名称。
parentIdNo父分类ID，来自 selectCategoryTreeList 返回的 Work Buddy 分类选择数据；不传则默认 ROOT。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses the creation action, the dependency on selectCategoryTreeList, and the default ROOT parent. While it doesn't mention permissions or side effects, the tool is simple (non-destructive create) and the description is sufficient.

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 concise sentences in Chinese, front-loaded with purpose. No redundant words; every sentence adds necessary information.

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?

For a simple tool with 2 parameters, no output schema, and no annotations, the description covers purpose, prerequisite call, parameter usage, and default behavior thoroughly. An agent can use it correctly without additional context.

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?

Schema coverage is 100% with descriptions for both parameters. The description adds value by specifying that parentId comes from selectCategoryTreeList and that omitting it defaults to ROOT. This complements the schema well.

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 '新增 SOP 分类' (create a new SOP category), with a specific verb (add/create) and resource (SOP category). This distinguishes it from sibling tools like selectCategoryTreeList (query categories) and uploadSop (upload files).

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 instructs to first call selectCategoryTreeList to let the user select a parent category and use its id as parentId. Also explains default behavior when parentId is omitted. This provides clear when-to-use and step-by-step 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