Skip to main content
Glama
adambbhe

kingdee_star

by adambbhe

kdy_list_invoice

Retrieve read-only invoice lists from Kingdee Cloud Star. Filter by bill type, invoice type, and date range to view sales or purchase invoices.

Instructions

查询发票列表(只读)。GET /jdy/v2/fi/invoice_fp。 销项/进项不是不同端点,用 bill_type / invoice_type 过滤。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sizeNo
end_dateNo
bill_typeNo
start_dateNo
invoice_typeNo
Behavior2/5

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

没有提供注释,因此描述必须完全承担行为透明度的责任。描述仅提到“只读”,没有说明返回格式、分页行为、可能需要的认证或其他副作用。对于无注释的工具,这明显不足,无法让代理充分了解调用该工具的影响。

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?

描述简短且直接,前三句分别说明核心功能、端点和过滤方式,没有冗余。信息密度高,结构清晰,易于快速理解。

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?

没有输出模式,描述需要提供返回相关上下文。但描述仅给出端点和过滤参数,未提及响应结构、分页细节、日期格式或其他必要信息。对于有6个参数且无注释的工具,这种描述不足以让代理成功调用和解析结果。

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

Parameters2/5

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

Schema描述覆盖率为0%,描述必须补偿。它解释了bill_type和invoice_type的用途(用于过滤),但其他参数(page、size、start_date、end_date)都没有在描述中说明。虽然参数有默认值,但代理无法从描述中理解这些参数的含义和格式,参数语义不完整。

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?

描述明确说明这是一个发票列表查询(只读),并给出具体端点,同时指出销项/进项不是不同端点,而是通过过滤参数区分,这让它与其他工具(如kdy_get_invoice、kdy_list_voucher)清楚区分。目的明确,动词和资源具体。

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?

描述提供了关于如何使用bill_type和invoice_type过滤的指导,并澄清了销项/进项不需要单独端点,这有助于选择。但它没有明确说明何时使用此工具与其他替代工具(如kdy_get_invoice),也没有给出排除条件。使用指引部分隐含,但不完整。

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adambbhe/kingdee-star-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server