Skip to main content
Glama
Sign In
zatca-mcp

zatca-mcp

by DoubleH10
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

render_invoice_html

Converts ZATCA invoice XML into a styled HTML document with embedded QR code for browser viewing or printing.

Instructions

Render a ZATCA invoice XML as a professional HTML document.

Takes a UBL 2.1 XML invoice (as generated by generate_invoice) and produces a styled HTML page with embedded QR code image, ready for viewing in a browser or printing.

Args: invoice_xml: Complete UBL 2.1 XML invoice string

Returns: Complete HTML document string with embedded styles and QR code image

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": {
      "invoice_xml": "<invoice_xml>"
    },
    "name": "render_invoice_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
invoice_xmlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It explains the output is a styled HTML document with embedded QR code, but does not explicitly confirm no side effects or state changes. For a rendering tool, this is acceptable.

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?

The description is concise (two sentences plus args/returns section), front-loaded with the main purpose, and well-structured with clear separation of input and output.

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?

Given a single parameter and the presence of an output schema, the description covers input, output, and usage context. It does not discuss error handling or limitations, but these are not critical for a simple render tool.

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?

With 0% schema description coverage, the description fully compensates by defining invoice_xml as 'Complete UBL 2.1 XML invoice string', adding meaning beyond the type alone.

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 specifies the verb 'render' and resources 'ZATCA invoice XML' and 'professional HTML document', clearly distinguishing it from siblings like generate_invoice (which produces XML) and check_compliance (compliance check).

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?

The description mentions input context: 'as generated by generate_invoice', implying a usage workflow. However, it does not explicitly state when not to use or list alternatives for similar tasks.

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

Deploy Server

Other Tools