Skip to main content
Glama
Sign In
Kingdee MCP Server

Kingdee MCP Server

by WaHaiLong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

kingdee_audit_bills

Audit pending documents in Kingdee ERP by providing form type and bill IDs. Returns success status and the audited bill IDs.

Instructions

审核单据（待审核 → 已审核）。

返回结构化结果：success=true 时表示单据已生效，next_action=null。

Returns: str: JSON，含 success / bill_ids 字段

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": {
      "params": "<params>"
    },
    "name": "kingdee_audit_bills"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations indicate non-destructive, non-idempotent operation. The description adds context by specifying the state change and return structure (success=true, next_action=null). No contradiction with annotations.

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 extremely concise: two sentences and a returns line. It is front-loaded with the action and result, with no superfluous text.

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 tool's simplicity (auditing bills) and the presence of an output schema, the description is mostly complete. However, it could mention batch processing (multiple bill_ids) and any error conditions.

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

Parameters2/5

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

The description does not describe the parameters. The input schema provides minimal descriptions in Chinese, but with schema description coverage at 0%, the tool description fails to add any meaning 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 verb (audit) and resource (bills), with a status transition (待审核 → 已审核). It distinguishes from sibling audit tools like kingdee_audit_production_orders and kingdee_unaudit_bills.

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 implies usage for auditing bills but does not explicitly state when to use this tool versus alternatives like kingdee_submit_bills or kingdee_create_and_audit. No when-not-to-use or prerequisites are mentioned.

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