Skip to main content
Glama
Frihet-io

Frihet MCP Server

Submit TicketBAI (Basque Country)

ticketbai_submit

Submit invoices to the Basque Country TicketBAI e-invoicing system. Auto-detects territory and returns TBAI ID and QR code for printing. Use sandbox for test submissions.

Instructions

Submit an invoice to the Basque Country TicketBAI e-invoicing system. Territory is auto-detected from the workspace address (Bizkaia → BATUZ/LROE, Gipuzkoa → Gipuzkoa TicketBAI, Araba → Araba TicketBAI). Returns the submission TicketBAI ID (TBAI identifier) and QR code URL for printing on the invoice.

Use sandbox=true for test submissions against the hacienda test endpoints. Production submissions require a valid TicketBAI certificate configured in workspace settings.

/ Envía una factura al sistema TicketBAI del País Vasco. El territorio se detecta automáticamente (Bizkaia→BATUZ/LROE, Gipuzkoa, Álava). Devuelve el identificador TBAI y URL del código QR para imprimir en la factura.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sandboxNoIf true, submits to the hacienda test endpoint instead of production. Default: false. / Si true, envía al entorno de pruebas de la hacienda. Por defecto: false.
invoiceIdYesFrihet invoice ID to submit / ID de la factura a enviar

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
csvYesCSV (Código Seguro de Verificación) returned by the hacienda foral
qrUrlYesQR code URL to print on the invoice (TBAI compliance)
acceptedYesWhether the hacienda foral accepted the submission
idempotentNoTrue if this echoes a prior already-accepted submission (no resubmission occurred)
tbaiIdentifierYesTicketBAI identifier (TBAI-XXXXX) returned by the hacienda foral
Behavior4/5

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

With all annotations false, description carries full burden. It discloses that submission is a write operation, requires a certificate for production, and returns TBAI ID and QR code URL. Could mention idempotency or error handling, but sufficient.

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?

Concise, well-structured with core functionality in first paragraph and usage instructions in second. Bilingual inclusion is appropriate. Every sentence adds value.

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?

Describes return values and prerequisites. Lacks error scenarios or handling of missing certificate, but given simple parameters and output schema existence, it is complete enough for basic usage.

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?

Schema coverage is 100%, so description adds value by explaining sandbox usage for test endpoints and territory auto-detection, reinforcing parameter meanings beyond schema.

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 it submits an invoice to the TicketBAI system, specifies the resource (invoice) and target system, and distinguishes from sibling tools by mentioning TicketBAI and auto-detected territory.

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?

Provides context for when to use (e-invoicing to Basque Country) and instructions for sandbox vs production. Does not explicitly mention alternatives like ksef_submit or conditions to avoid, but overall guidance is clear.

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/Frihet-io/frihet-mcp'

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