yimu-mcp

save_child_category

save_child_category

Create or update a child category in Yimu bookkeeping to organize subcategories under a parent category. Specify the category ID to update an existing one or omit it to add a new category.

Instructions

新增或更新二级分类（POST /childCategory/addOrUpdateChildCategory，upsert：带主键为更新）。entity 字段：categoryId 主键；categoryName 名称；iconUrl 图标；parentCategoryId 所属一级分类；positionWeight 排序；hide 隐藏；categoryType 类型

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": {
      "entity": "<entity>"
    },
    "name": "save_child_category"
  }
}

Input Schema

Name	Required	Description	Default
`entity`	Yes	二级分类对象

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Sep 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly exposes the mutating nature via '新增或更新', the POST method, and the upsert behavior where a primary key triggers an update. It does not mention response details or validation effects, but the core side-effect is well disclosed.

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 compact and efficient: one sentence states the operation, endpoint, and upsert behavior, and the second lists the data fields. Every sentence contributes useful information with no filler or redundancy.

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?

Given the extremely thin schema and lack of annotations, the description compensates well by defining the upsert semantics and the entity field meanings. It is sufficient for an agent to understand how to structure a call, though it omits explicit constraints or value formats for fields like hide and categoryType.

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

Parameters5/5

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

The schema only defines entity as a generic object with no properties, so the description provides essential semantics by enumerating all meaningful fields: categoryId, categoryName, iconUrl, parentCategoryId, positionWeight, hide, and categoryType. This is high-value information that the input schema alone completely lacks.

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 a specific operation: creating or updating a second-level category, with the exact HTTP endpoint and upsert semantics. This makes it easily distinguishable from sibling tools like save_parent_category and delete_child_category.

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

Usage Guidelines4/5

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

The description implies when to use the tool: any time a child category needs to be added or updated, and the upsert note clarifies whether the operation will insert or update based on presence of categoryId. It does not explicitly say when not to use it or name alternatives, so it stops short of full guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.