Skip to main content
Glama
Sign In
Kingdee MCP Server

Kingdee MCP Server

by WaHaiLong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

kingdee_usage_stats

Read-onlyIdempotent

Retrieve aggregated usage statistics for the current session, including tool usage counts, success/failure rates, total time, and error breakdown.

Instructions

获取当前会话的使用统计摘要。

返回当前进程内聚合的统计数据：

  • 工具使用次数

  • 成功/失败次数

  • 累计耗时

  • 错误类型统计

Returns: str: 统计数据的 JSON 格式

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kingdee_usage_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already provide readOnly, idempotent, and non-destructive hints. The description adds useful behavioral context about the aggregated statistics returned (success/failure counts, time, errors), enhancing transparency beyond the annotations.

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 very concise, using bullet points for key statistics. Every sentence is necessary and no redundancy. Front-loads the purpose and clearly explains output.

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 no parameters and an output schema exists, the description adequately covers the return value format. It lists the statistics included, but does not specify the exact JSON structure. Still sufficient for an agent to understand the output.

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?

There are no parameters, so the schema fully covers them. The description adds no parameter-specific information, which is appropriate. With 0 parameters, the baseline is 4.

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 retrieves usage statistics for the current session, listing specific aggregated metrics. It is distinct from sibling tools which are CRUD or query functions for business entities.

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 implicitly indicates when to use (when needing session usage stats) but does not explicitly state when not to use or list alternatives. The context makes it clear, but lacks direct 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