Skip to main content
Glama
asgard-ai-platform

MCP Universal EC E-Invoice Server

create_b2c_allowance

Creates a B2C allowance (credit note) in positional field format (D0401), accepting buyer details and line items, and returns the API response.

Instructions

Create a B2C allowance using positional field format (D0401). Returns the API response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesList of allowance items. Each item: {D1: seq, D2: original_date, D3: original_inv_number, D4: seq_number, D5: description, D6: qty, D8: unit_price, D9: amount, D10: tax, D11: tax_type}.
buyer_idYesBuyer identifier (tax ID or empty string).
buyer_nameYesBuyer name.
tax_amountYesTax amount (C2).
buyer_emailNoBuyer email (B7).
total_amountYesTotal amount (C3).
buyer_addressNoBuyer address (B3).
allowance_dateYesAllowance date (YYYYMMDD).
allowance_typeYesAllowance type ('2'=seller notice).
buyer_facsimileNoBuyer facsimile (B6).
buyer_telephoneNoBuyer telephone (B5).
allowance_numberYesAllowance number.
buyer_role_remarkNoBuyer role remark (B9).
original_buyer_idNoOriginal buyer ID (C5).
original_seller_idNoOriginal seller ID (C4).
buyer_customer_numberNoBuyer customer number (B8).
buyer_person_in_chargeNoBuyer person in charge (B4).
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It only states 'Returns the API response' without detailing side effects, auth requirements, rate limits, or what the response contains. This is insufficient for a creation 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 one short sentence, front-loaded with the tool's purpose. However, it could include more useful information without becoming verbose.

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 17 parameters (8 required), no output schema, and no annotations, the description is incomplete. It does not explain what a B2C allowance is, error handling, or provide any context for usage.

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 baseline is 3. The description adds 'positional field format (D0401)' but does not explain parameters beyond what the schema already provides. No additional semantics.

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 'Create a B2C allowance', specifying the verb and resource. It also includes the positional field format (D0401), which distinguishes it from the sibling tool create_b2c_allowance_named that likely uses named fields.

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 alternatives like create_b2c_allowance_named or create_b2b_allowance. There is no mention of prerequisites, context, or when not to use it.

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