Skip to main content
Glama

xbrl_statement_normalizer

Read-onlyIdempotent

[Deterministic XBRL financial statement normalizer. Pure calculation & parsing, read-only, side-effect free]. Parses and normalizes raw European XBRL instance documents (IT OIC, DE HGB, FR PCG, EU IFRS) into standardized financial indicators: EBITDA, EBIT, Net Financial Debt (PFN), Working Capital (CCN), Solvency ratio, and Current ratio with decimal.js precision. Usage: Use this tool to ingest statutory annual reports and extract comparable financial ratios for credit, M&A, or vendor due diligence. Returns: JSON object with { reportingStandard: string, companyName: string, fiscalYear: number, reclassifiedBalanceSheet: object, reclassifiedIncomeStatement: object, financialRatios: object, creditRiskIndicator: object }.

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": {
      "companyVatOrId": "<companyVatOrId>",
      "reportingYear": "<reportingYear>"
    },
    "name": "xbrl_statement_normalizer"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportingYearYesFinancial statement reporting fiscal year
companyVatOrIdYesCompany national tax ID or VAT number
taxonomyStandardNoAccounting taxonomy standard (default: XBRL_OIC_ITALY)
financialsSummaryNoPre-parsed structured financial inputs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint and idempotentHint, so 'read-only, side-effect free' is largely restatement; the added value is the determinism and decimal.js precision claim plus the list of supported taxonomies. However, it never explains how a 'raw XBRL instance document' is actually supplied, given the required inputs are a VAT/ID and a year, which leaves real behavioral uncertainty about the ingestion path.

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

Conciseness4/5

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

The labeled sections (preamble, Usage, Returns) are front-loaded and easy to scan, and the Returns block earns its space because no output schema exists. The bracketed preamble partly duplicates the annotations, which is mild waste.

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?

For a tool with four parameters, a nested eleven-field object, and no output schema, the description does the important work: it spells out the return object's keys and the indicator set. The remaining gap is the unresolved relationship between 'parses raw XBRL instance documents' and the pre-parsed financialsSummary input, which an agent would need to resolve before first use.

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 description coverage is 100%, so the schema already documents all four parameters and the eleven nested financial fields, making 3 the baseline. The description adds only taxonomy breadth (including 'FR PCG', which has no matching enum value) and does not clarify the role or optionality of financialsSummary relative to the 'raw XBRL' framing.

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 names a specific verb and resource ('Parses and normalizes raw European XBRL instance documents') and enumerates the exact outputs (EBITDA, EBIT, PFN, CCN, solvency, current ratio). This is clearly distinguishable from validator- or calculator-style siblings in the catalog.

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?

It gives a concrete usage context — 'ingest statutory annual reports and extract comparable financial ratios for credit, M&A, or vendor due diligence' — which tells the agent when the tool is appropriate. It stops short of exclusions or naming an alternative when a plain ratio calculator would suffice, so it is not a 5.

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