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

mcp-einvoicing-be

by cmendezs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_reference_qualifier_codes

List UNCL1153 reference qualifier codes from the CEF EN 16931 code list. Get valid codes for referencing documents in e-invoices.

Instructions

List UNCL1153 reference qualifier 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_reference_qualifier_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden for behavioral disclosure. It accurately describes a read-only listing operation, but does not mention whether the list is complete, sorted, or limited, nor what each returned item contains beyond what the output schema already covers.

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?

A single informative sentence with no filler. The verb and subject appear first, and the source qualifier is presented immediately, making the purpose readable at a glance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter listing tool with an output schema present, the description is sufficient. It names the exact code list source and action, and the output schema handles return value details, leaving no meaningful gap for an agent to invoke it incorrectly.

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 tool has zero parameters and the schema description coverage is 100%, so the schema fully defines the input surface. The description reinforces that no input is needed by framing this as a simple enumeration, adding no necessary parameter context.

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 states a specific verb ('List') and resource ('UNCL1153 reference qualifier codes') and identifies the exact source (CEF EN 16931 code list). This clearly distinguishes the listing behavior from the sibling check_reference_qualifier_code and from other list_*_codes tools.

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 gives no guidance on when to use this tool versus the nearby check_reference_qualifier_code or other list tools. It is implied by the name and sibling pattern, but there is no explicit context for selection.

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