No user-submitted related servers found.
Scored across 17 tools
Each tool targets a clearly defined concern: status, reference rates, tax tables, validation, calculation, XML handling, error translation, and a generic fallback. Even calcular_tributos vs calcular_com_trilha are explicitly differentiated as calculation vs observability/trace. The generic rtc_chamar is clearly scoped to endpoints without dedicated tools, so it does not create ambiguity.
All tools share the rtc_ prefix and snake_case, which creates a strong, predictable pattern. However, the set mixes verb-led names like rtc_calcular_tributos and rtc_validar_ncm with noun/resource-led names like rtc_status and rtc_base_calculo_mercadorias, so it is not a uniform verb_noun pattern throughout.
With 17 tools, the set is slightly above the ideal 3-15 range, but each tool covers a meaningful part of the tax calculation/validation workflow. The count feels justified by the broad domain rather than bloated, and the generic rtc_chamar avoids needing dozens of thin wrappers.
The surface covers status, reference data, tax tables, legal basis, validation, calculation, calculation traces, base-amount inspection, XML generation/validation, and error handling. The generic rtc_chamar fills any remaining API endpoint gaps, so there are no dead ends in the stated domain.