Skip to main content
Glama
Sign In
Kingdee MCP Server

Kingdee MCP Server

by WaHaiLong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

kingdee_query_sale_orders

Read-onlyIdempotent

Query sales order records from Kingdee Cloud Star ERP with customizable filters and field selection to retrieve order details.

Instructions

查询销售订单（SAL_SaleOrder）列表。

常用 filter_string：

  • 已审核: "FDocumentStatus='C'"

  • 指定客户: "FCustId.FNumber='C001'"

推荐 field_keys： FID,FBillNo,FDate,FDocumentStatus,FCustId.FName,FSalesOrgId.FName,FTotalAmount

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

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 and idempotentHint=true, so the description's role is lighter. It adds context by stating the return format (JSON) and providing filter/field examples, but does not disclose additional behavioral traits beyond what annotations imply.

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 concise and well-structured: first a clear statement of purpose, then practical filter and field examples, then the return type. Every sentence serves a purpose without 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 moderate complexity of the query tool and the presence of an output schema, the description covers essential aspects. It might be slightly improved by mentioning pagination or sorting, but current content is sufficient for typical use cases.

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?

Schema descriptions cover all parameters, but the tool's description adds value by showing concrete examples for 'filter_string' and 'field_keys', complementing the schema. This helps the agent understand typical usage patterns.

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 title and description clearly state the tool queries sale orders (SAL_SaleOrder) list, using specific verb+resource. The mention of the form ID distinguishes it from sibling query tools.

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 provides practical examples of common filter strings and recommended field keys, aiding correct usage. However, it does not explicitly compare with alternative query tools or provide when-not-to-use guidance.

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