Skip to main content
Glama
Sign In
Kingdee MCP Server

Kingdee MCP Server

by WaHaiLong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

kingdee_query_stock_bills

Read-onlyIdempotent

Query inbound and outbound stock documents such as purchase receipts and sales deliveries from Kingdee ERP with filters, field selection, and pagination.

Instructions

查询出入库相关单据。

form_id 常用取值：

  • STK_InStock: 采购入库单

  • SAL_OUTSTOCK: 销售出库单

  • STK_MisDelivery: 其他出库单

  • STK_Miscellaneous: 其他入库单

  • STK_TransferDirect: 直接调拨单

Returns: str: JSON 格式的出入库单列表

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, covering safety. Description adds return type (JSON string) but does not elaborate on pagination behavior or result structure beyond schema.

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 short sentences plus a bullet list of form_id examples, all front-loaded and efficient with no fluff.

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 has many parameters and an output schema, the description covers the core purpose and common form_ids; could mention pagination behavior but overall sufficient.

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?

Description adds value by listing common form_id values beyond the schema's generic description; however, other parameters like filter_string and field_keys are not explained further, though schema descriptions are present.

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?

Description clearly states the tool queries inbound/outbound documents (出入库单据) and lists common form_id values for specific stock movements, distinguishing from general query tools like kingdee_query_bills.

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?

Provides explicit form_id examples for common stock scenarios (e.g., STK_InStock for purchase receipt), but lacks guidance on when not to use this tool or alternatives among many sibling query tools.

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