Skip to main content
Glama
Sign In
mcp-einvoicing-be

mcp-einvoicing-be

by cmendezs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_vatex_codes

Retrieve VAT exemption reason codes from the CEF EN 16931 list to identify valid VATEX codes for e-invoicing.

Instructions

List VATEX (VAT exemption reason) codes from the CEF EN 16931 code list.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. The verb 'List' implies a read-only retrieval and the source is specified, but it does not explicitly state that all codes are returned, any ordering behavior, or that there are no side effects. There is no contradiction, but the disclosure is minimal.

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 one sentence and about 14 words, front-loaded with the verb and resource, and includes the acronym expansion without fluff. Every word earns its place.

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?

For a simple zero-parameter list tool with an output schema present, the description is nearly complete: it states the resource and the relevant standard. A note that it returns the full code set or a pointer to check_vatex_code for single-code validation would make it fully complete, but those are minor gaps.

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?

The input schema has zero properties, so there are no parameters whose semantics need explanation, and schema description coverage is trivially 100%. This meets the baseline for a no-parameter tool with nothing missing.

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 uses a specific verb ('List'), a specific resource ('VATEX codes'), expands the acronym ('VAT exemption reason'), and names the source code list ('CEF EN 16931 code list'). This clearly distinguishes it from sibling tools like list_vat_category_codes and check_vatex_code.

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 intended use case is clear: when the full set of VAT exemption reason codes is needed. It does not explicitly mention when to use check_vatex_code instead or state any exclusions, but for a zero-parameter list tool the context is straightforward.

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