yimu-mcp

save_asset

save_asset

Add a new asset or update an existing one in a Yimu bookkeeping ledger. Provide asset fields such as name, type, balance, and total quota; include the asset ID to modify an existing record.

Instructions

新增或更新资产（POST /asset/addOrUpdateAsset，upsert：带主键为更新）。entity 字段：assetId 主键；assetName 名称；assetType 类型；assetNumber 余额；totalQuota 总额度；intoTotalAsset 计入总资产；hide 隐藏；bookId 账本；currency 币种；remark/simpleName/cardCode/positionWeight 可选；userId/updateTime 自动填充

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_asset"
  }
}

Input Schema

Name	Required	Description	Default
`entity`	Yes	资产对象

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Sep 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the mutation behavior (upsert), the HTTP endpoint, and that userId/updateTime are automatically filled, which goes beyond the input schema. It does not mention authentication or response details, but the core behavioral traits are visible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense sentence that front-loads the operation and endpoint before listing fields. The field list is necessary and not padded with filler. Slight structure loss from the run-on format, but it is efficient and information-dense.

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 no output schema and no annotations, the description covers the endpoint, upsert behavior, update-vs-insert detection, and complete field semantics, which is enough for an agent to construct a valid call. It omits the response/return shape and auth context, which would be needed for full completeness, but the main invocation requirements are satisfied.

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 input schema only describes entity as an object, providing no property-level details. The description compensates richly by naming assetId as primary key, explaining each field's business meaning, marking optional fields, and noting which fields are auto-populated. This is a substantial addition beyond the 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 action: 新增或更新资产 (add or update an asset), specifies the endpoint POST /asset/addOrUpdateAsset, and explains upsert semantics with the primary key determining update. This makes it easy to distinguish from sibling tools like delete_asset, get_assets, and save_asset_history.

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 gives a concrete rule: if the entity carries the primary key assetId, the operation updates; otherwise it creates. It also enumerates the asset fields so an agent knows what kind of object to pass. It does not explicitly name alternatives or exclusion conditions, but the usage context is clear enough.

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