Skip to main content
Glama
asgard-ai-platform

MCP Universal EC E-Invoice Server

create_b2c_invoice

Create a Taiwan B2C e-invoice with mandatory buyer, line item, and tax data; API returns the invoice creation response.

Instructions

Create a B2C invoice using positional field format (C0401). Returns the API response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesList of invoice line items. Each item: {B1: seq, B2: description, B3: qty, B5: unit_price, B6: amount, B7: tax_type, B13: tax_amount}.
totalYesTotal amount including tax.
buyer_idYesBuyer identifier (tax ID or empty string).
currencyNoCurrency code (e.g. 'USD').
discountNoDiscount amount.
free_taxYesTax-exempt sales amount.
tax_rateYesTax rate (e.g. '0.05').
tax_typeYesTax type ('1'=taxable, '2'=zero-rate, '3'=exempt, '9'=mixed).
zero_taxYesZero-tax-rate sales amount.
donate_toNoNPO ban (love code) when donating.
buyer_nameYesBuyer name.
print_markYesPrint mark ('Y' or 'N').
tax_amountYesTax amount.
carrier_id1NoCarrier ID primary (encoded).
carrier_id2NoCarrier ID secondary (plain).
donate_markYesDonate mark ('1'=donate, '0'=no).
main_remarkNoMain remark.
carrier_typeNoCarrier type (e.g. '3J0002' for mobile barcode).
invoice_dateYesInvoice date (YYYYMMDD).
invoice_timeYesInvoice time (HHmmss).
invoice_typeYesInvoice type code (e.g. '07').
sales_amountYesTaxable sales amount.
exchange_rateNoExchange rate.
random_numberYes4-digit random number.
invoice_numberYesInvoice number (e.g. 'AB12345678').
zero_tax_reasonNoZero-tax-rate reason code.
customs_clearanceNoCustoms clearance mark.
original_currency_amountNoOriginal currency amount.
Behavior2/5

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

With no annotations, the description carries full burden. It only states that the tool returns an API response, but does not disclose side effects, error conditions, authentication needs, or the effects of creating an invoice. This is minimal transparency for a mutation tool.

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?

The description is a single concise sentence that front-loads the core purpose and format. No unnecessary words, but could include more structural cues like preconditions or output summary.

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 the high complexity (28 parameters, 17 required) and lack of output schema or annotations, this short description provides insufficient context. Important details like the meaning of 'positional field format' and the structure of the API response are omitted.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters. The tool description adds no additional parameter-level information beyond the schema, justifying a baseline of 3.

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 it creates a B2C invoice and mentions a specific format ('positional field format (C0401)'). This distinguishes it from related tools like create_b2c_invoice_named, though it does not explicitly contrast them.

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 is provided on when to use this tool versus any of the 26 sibling tools, such as create_b2c_invoice_named or create_b2c_allowance. The description lacks context about prerequisites or use cases.

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/asgard-ai-platform/mcp-universalec-e-invoice'

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