yimu-mcp

delete_parent_category

delete_parent_category

Delete a first-level category from a Yimu bookkeeping ledger by providing its categoryId and userId. Removes the parent category and associated data.

Instructions

删除一级分类（POST /parentCategory/deleteParentCategory）。entity 需携带主键字段（categoryId）与 userId。

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

Input Schema

Name	Required	Description	Default
`entity`	Yes	一级分类对象（含主键 categoryId）

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Sep 15, 2026

TDQS

A3.8/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It confirms a destructive action and states the HTTP method, but does not mention cascading effects on child categories, reversibility, soft-delete behavior, authentication requirements, or potential errors that would be important for a delete operation.

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 compact sentence that packs the action, endpoint, and required entity fields together with no filler. Every part earns its place, and the key information is front-loaded.

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 simple one-parameter delete tool, the description provides enough to construct the request: the endpoint and the required fields. However, it omits behavioral details such as whether the deletion cascades to child categories, what the response looks like, and any error or auth implications. It is minimally viable but not fully complete.

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 says the entity is a parent category object containing the primary key categoryId. The description adds the crucial requirement that userId must also be included, which is not discoverable from the schema. This extra detail is essential for correct invocation.

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 explicitly states the action ('删除一级分类') and includes the endpoint, making the tool's purpose unmistakable. It also distinguishes it from sibling tools like delete_child_category and delete_parent_category's counterpart save_parent_category.

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 makes the target resource clear ('一级分类') but does not explicitly state when to prefer this over alternatives, nor does it mention exclusions or prerequisites. Usage is implied by the name and category type, but no direct guidance is provided.

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