Skip to main content
Glama
Frihet-io

Frihet MCP Server

Get FACe Submission Status

face_status
Read-onlyIdempotent

Poll the status of a Spanish B2G invoice submitted to FACe. Provide the invoice ID to get the current state code, description, and registration number.

Instructions

Poll the status of a FACe (Spain B2G) invoice submission. Returns the current FACe portal state code, description, and the registro number.

Common FACe status codes: • 1200 — Registrada / Registered (submission received) • 1300 — En proceso de contabilización / In accounting (being processed) • 1400 — Contabilizada / Accounted (approved, awaiting payment) • 2400 — Anulada / Cancelled • 3100 — Rechazada / Rejected (check rejectionReason)

/ Consulta el estado de un envío a FACe. Devuelve el código de estado, descripción y número de registro.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codigoYesFACe status code (e.g. '1200'=Registrada, '1400'=Contabilizada, '3100'=Rechazada)
motivoYesReason/motive associated with the current status (e.g. rejection motive)
descripcionYesHuman-readable FACe status description
numeroRegistroYesFACe registration number for this submission
estadoTramitacionYesFACe processing-state code (estado de tramitación)
Behavior4/5

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

Annotations already declare read-only, and description adds polling behavior and common status codes, enhancing transparency without contradiction.

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, bilingual, well-structured with bullet list of status codes; no wasted words.

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?

Given output schema exists, description sufficiently covers return details and usage context; complete for a poll tool.

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?

Single parameter with full schema coverage; description adds context that it's the same ID as face_submit, providing extra 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?

Clearly states it polls the status of a FACe invoice submission, distinguishing it from siblings like face_submit and get_einvoice_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies use after face_submit but lacks explicit when-to-use or alternatives, leaving some ambiguity.

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