Skip to main content
Glama
Sign In
Kingdee MCP Server

Kingdee MCP Server

by WaHaiLong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

kingdee_query_product_standard_cost

Read-onlyIdempotent

Query product standard costs from Kingdee Cloud Star ERP. Filter by material and cost version to retrieve specific cost details.

Instructions

查询产品标准成本（STD_ProductCostQuery）。

常用 filter_string：

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

  • 指定成本版本: "FCostVersionId.FNumber='STD01'"

推荐 field_keys： FMaterialId.FNumber,FMaterialId.FName,FUnitId.FName,FStdCost,FMaterialCost,FLabourCost,FFeeCost

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.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. The description adds that it returns a JSON list and mentions the function name, but does not contradict annotations. It provides adequate but not deep behavioral context beyond what annotations offer.

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 concise (three lines) and front-loaded with the main purpose. It includes the function name and practical examples without unnecessary verbosity. No wasted sentences.

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 is a read-only query with comprehensive annotations and an output schema, the description covers the purpose, common usage patterns, and return type. It does not detail error handling or pagination, but these are secondary for a simple query; completeness is adequate.

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

Parameters3/5

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

The description provides example filter_string and field_keys values, adding some meaning beyond the schema. However, the schema already has comprehensive descriptions for all parameters (though context reports 0% coverage, likely meaning description does not systematically cover parameters). Baseline 3 is appropriate as schema covers parameters and examples add minimal extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool queries product standard cost (查询产品标准成本) and provides the Kingdee function name. It uses a specific verb and resource, but does not explicitly differentiate from sibling cost query tools, though the name itself is specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives examples of common filter_string and field_keys, implying typical usage, but lacks explicit guidance on when to use this tool versus alternative cost-related queries (e.g., material cost, finished product cost). No when-not-to-use or prerequisites are stated.

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