Skip to main content
Glama
cmendezs

mcp-fattura-elettronica-it

export_to_json

Serialize parsed FatturaPA invoice data into clean, indented JSON format. Control indentation and choose whether to include empty fields.

Instructions

Serialize a parsed FatturaPA dict to a clean, indented JSON string.

Call this after parse_fattura_xml() when you need a human-readable or machine-transferable representation of the invoice. By default, null/empty fields are omitted (include_empty=False) to reduce noise in the output.

indent controls JSON indentation (0 = compact, 2 = standard readable, 4 = wide). include_empty=True retains all keys even when their value is null or empty string.

Always succeeds. Returns {'json_string': str, 'size_chars': int}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parsed_fatturaYesParsed FatturaPA dict as returned by parse_fattura_xml(). Will be serialised to a clean, indented JSON string.
indentNoJSON indentation level (0–8 spaces). Default 2.
include_emptyNoInclude fields with null/empty values in output. Default False.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, but description covers default behavior (omitting null/empty fields), indentation control, guarantee of success, and return format (JSON string and size). No destructive traits.

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 description with clear purpose first, followed by usage, parameters, and behavior. No unnecessary 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?

Description fully covers inputs, behavior, and output for this simple tool, especially given output schema exists. No missing details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and description adds meaning: explains parsed_fattura as output of parse_fattura_xml, gives examples for indent values, and describes include_empty default.

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?

Description clearly states the tool serializes a parsed FatturaPA dict to JSON, using specific verb 'Serialize' and resource, distinguishing it from sibling tools which focus on XML creation/validation.

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?

Description explicitly says to call after parse_fattura_xml() when a human-readable or transferable representation is needed, providing clear context. No explicit exclusion but context suffices.

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/cmendezs/mcp-fattura-elettronica-it'

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