Skip to main content
Glama
Sign In
Kingdee MCP Server

Kingdee MCP Server

by WaHaiLong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

kingdee_query_misc_movement_detail

Read-onlyIdempotent

Query miscellaneous movement details for stock in/out transactions, including other inbound and outbound records. Filter by date, material, or warehouse to retrieve specific data.

Instructions

查询杂项出入库明细表（STK_MiscMovementDetail）。

用于查看杂项出入库的明细数据，包括其他入库、其他出库等。

常用 filter_string：

  • 指定日期范围: "FBillDate>='2024-01-01' and FBillDate<='2024-12-31'"

  • 指定物料: "FMaterialId.FNumber='MAT001'"

  • 指定仓库: "FStockId.FNumber='WH01'"

推荐 field_keys（默认已包含关键字段）： FID,FBillNo,FBillDate,FDocumentStatus,FStockOrgId.FName, FMaterialId.FNumber,FMaterialId.FName,FUnitId.FName,FQty,FPrice,FAmount

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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, so the description adds no contradictions. It adds that the return is a JSON-formatted list, which is useful but not critical beyond annotations.

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 well-structured with sections for purpose, examples, and recommended fields. It is somewhat verbose due to the code block but remains clear and informative. No unnecessary repetition.

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?

For a query tool with pagination and filtering, the description covers the core usage with examples. It does not detail the output schema (though one exists) or explain pagination parameters, but the schema provides defaults. Overall, it is reasonably complete given the complexity.

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 description coverage is 0% for the top-level parameter, but nested property descriptions exist in the schema. The description adds value by giving concrete filter_string and field_keys examples. However, it does not explain the required form_id parameter (which should likely be set to 'STK_MiscMovementDetail' based on the table name), potentially causing confusion.

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 queries the miscellaneous movement detail table (STK_MiscMovementDetail) for viewing inbound/outbound details. It uses a specific verb '查询' (query) and resource, distinguishing it from sibling query tools like kingdee_query_bills or kingdee_query_inventory.

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 concrete filter_string examples and recommended field_keys, helping the agent construct queries. However, it does not explicitly state when to use this tool vs. other query tools (e.g., for general bills vs. misc movement), though the table name makes it clear.

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