Skip to main content
Glama
Sign In
@ktmcp/beezup

@ktmcp/beezup

by ktmcp-cli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

GenerateOrderInvoice

Generate an order invoice by sending the request body to the BeezUP Merchant API. This action creates an invoice for an order.

Instructions

Generate an Order Invoice

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": "GenerateOrderInvoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoRequest body

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states 'Generate an Order Invoice' without revealing side effects, authorization needs, or whether the action is read-only or destructive. This is insufficient for safe invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely terse (one sentence) but fails to provide necessary context. It is under-specified given the complexity of the input schema (nested object) and the lack of output schema. Brevity here sacrifices clarity.

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 omits essential details: what the tool returns (PDF, ID, status?), what fields the 'body' should contain, and how it relates to sibling tools like 'GetOrderInvoicePdf'. This incompleteness hinders correct usage.

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?

Although schema description coverage is 100% for the 'body' parameter, the tool description adds no additional meaning. The parameter is simply labeled 'Request body' with no elaboration on expected structure, required subfields, or examples, leaving the agent underinformed.

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

Purpose2/5

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

The description 'Generate an Order Invoice' is a tautology of the tool name 'GenerateOrderInvoice', adding no explanatory value. It fails to differentiate from the sibling tool 'GenerateBatchOrderInvoice', leaving ambiguity about whether this is for single vs. batch invoice generation.

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 provides no guidance on when to use this tool over alternatives like 'GetOrderInvoicePdf' or 'GenerateBatchOrderInvoice'. There is no mention of prerequisites, context, or scenarios where this tool is appropriate.

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