Skip to main content
Glama
Sign In
Kingdee MCP Server

Kingdee MCP Server

by WaHaiLong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

kingdee_query_workflow_status

Read-onlyIdempotent

Get the approval workflow status and details for a specific document using its form ID and bill ID.

Instructions

查询单据的审批流状态。

返回单据当前的审批状态和单据详情。

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already indicate read-only and idempotent behavior. Description adds that return is JSON string, but omits details like whether the document must exist or what happens if not found.

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?

Description is very short and front-loaded with purpose. However, it mixes Chinese and English, and the Returns block is redundant. Could be slightly more structured.

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?

Given an output schema exists, description doesn't need to detail return structure, but it omits important context like possible statuses, error conditions, and behavior with non-existent documents.

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% according to context, and the description does not explain parameters (form_id, bill_id) or their values. Parameter purposes are only inferred from brief schema labels.

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 approval flow status and returns status and details. It differentiates from siblings like kingdee_query_approval_flow only by name, not explicitly.

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?

No guidance on when to use this tool versus alternatives like kingdee_query_approval_flow or kingdee_view_bill. Missing context for prerequisites or typical use cases.

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