Skip to main content
Glama
berthelius

Frihet MCP Server

Get TicketBAI Submission Status

ticketbai_status
Read-onlyIdempotent

Poll the Basque tax authority for TicketBAI invoice acknowledgement status. Returns accepted, rejected, submitted, or error state.

Instructions

Poll the hacienda acknowledgement status for a TicketBAI submission. Returns the TBAI identifier, territory, and hacienda's confirmation or rejection state.

Common status values: • submitted — sent, awaiting hacienda response (check again in 30-60s) • accepted — hacienda confirmed the submission (AEAT/foral treasury received) • rejected — hacienda rejected (check rejectionReason for correction guidance) • error — internal processing error (see error field)

/ Consulta el estado de acuse de recibo de la hacienda foral para un envío TicketBAI. Devuelve el identificador TBAI, territorio y estado de confirmación o rechazo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
invoiceIdYesFrihet invoice ID (same as used in ticketbai_submit) / ID de la factura

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
csvYesCSV (Código Seguro de Verificación) for the submission
qrUrlYesQR code URL to print on the invoice (null if not yet available)
errorsYesHacienda error messages if rejected (null if none)
estadoYesCurrent submission status stored server-side (e.g. 'accepted', 'rejected')
acceptedYesWhether the submission has been accepted by the hacienda foral
submittedAtYesISO 8601 timestamp the submission was recorded (null if unknown)
tbaiIdentifierYesTicketBAI identifier
Behavior5/5

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

Adds polling behavior and status semantics beyond readOnlyHint/idempotentHint annotations. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose but bilingual text doubles length. Could be more concise.

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?

With output schema and annotations, description covers polling details, statuses, and guidance adequately.

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 covers invoiceId fully. Description adds cross-reference to ticketbai_submit but minimal additional meaning.

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?

Clear verb (Poll) and resource (TicketBAI submission status). Distinct from sibling tools like ticketbai_submit, face_status, verifactu_status.

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 status interpretations and polling guidance (30-60s for submitted). Missing explicit when-not-to-use or alternatives.

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

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