Skip to main content
Glama

Propose sending an invoice to SPV (e-Factura)

invoices_send_efactura

[Invoicing changes] Propose sending an issued invoice to SPV (ANAF e-Factura) through the invoicing account. Refused for cancelled or draft invoices and for invoices already in SPV. ANAF may take minutes to answer: read the state afterwards with invoices_get (efactura_status). Simulated first; nothing is sent until the seller approves (asked in the conversation, confirmed with manage_action). Works on: Demo invoicing (sample data).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "series": "<series>",
      "number": "<number>"
    },
    "name": "invoices_send_efactura"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYes
seriesYes
accountNoAccount id from list_accounts. Optional when only one account is connected.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations (which only say non-read-only, non-destructive, non-open-world), the description discloses that execution is simulated first, that nothing leaves until seller approval, that ANAF may take minutes to respond, and which invoices are rejected. It does not spell out what happens on a repeated call or what the proposal returns, which are the only notable gaps for a mutation tool.

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?

Four short sentences, front-loaded with purpose, then refusal conditions, then the async/verification path, then the simulation caveat. Every sentence carries distinct operational information; there is no restatement of the title or the schema.

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 simulated-then-approved external submission with three parameters and an available output schema, the description covers what an agent needs: preconditions, refusal cases, the approval gate, the latency and where to re-check state, and the supported environment ('Demo invoicing'). Return values are rightly omitted since an output schema exists.

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 coverage is only 33%: only 'account' carries a schema description ('Account id from list_accounts... optional when only one account is connected'), and the description adds nothing about it. The two required parameters, series and number, are undocumented anywhere, though they are conventional invoice identifiers that the domain makes inferable.

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 ('Propose sending') plus a precisely scoped resource ('an issued invoice to SPV (ANAF e-Factura) through the invoicing account'). It makes clear this is a proposal/simulation step rather than an immediate send, which distinguishes it from a plain send or issue tool, and it names invoices_get as the follow-up reader.

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

Usage Guidelines5/5

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

It states explicit exclusions — refused for cancelled or draft invoices and for invoices already in SPV — and gives the correct follow-up path ('read the state afterwards with invoices_get (efactura_status)'). The approval flow (seller asked in conversation, confirmed with manage_action) tells the agent exactly what sequence to follow rather than leaving routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources