Skip to main content
Glama
Sign In
kingdee-mcp

kingdee-mcp

by kknocookie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

query_so_mo_relation

Check links between sales orders and manufacturing orders, showing completion status, delivery risk, and picking details.

Instructions

查询销售订单与生产工单的关联关系，包含完工状态、交货风险和领料情况。

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "query_so_mo_relation"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
end_dateYes
start_dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden. It accurately describes the function as a query, but lacks details on default limits, possible pagination, or read-only nature. The behavior is implied but not fully transparent.

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 a single sentence that immediately states the purpose and included aspects. No redundant words; every part contributes to understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks essential details for a query with date range and optional limit parameters. It does not explain how parameters filter results, nor does it mention default limit or output structure (despite having an output schema). The description is insufficient for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate. However, it does not explain the parameters (start_date, end_date, limit) or how they relate to the output content. The description adds no value beyond the schema titles.

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 relationship between sales orders and production work orders, listing three included aspects (completion status, delivery risk, material picking). It distinguishes from siblings like query_delivery_risk and query_material_shortage by focusing on the SO-MO relationship.

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 the tool is used to retrieve SO-MO relations but does not explicitly state when to use it over alternatives like query_delivery_risk or export_so_mo_report. No exclusions or conditional usage 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