Valida XML TISS ou lote em JSON. Quando usar: antes de gerar ou enviar um lote. Quando não usar: para corrigir achados sem aplicar o ciclo validar → tiss_apply_fixes → validar de novo.
| Name | Required | Description | Default |
|---|---|---|---|
| xml | No | ||
| data | No | ||
| lote | No | Schema estrutural disponível em tiss://schemas/lote. | |
| contexto | No | ||
| operadora | No |
| Name | Required | Description | Default |
|---|---|---|---|
| valid | Yes | ||
| decisao | No | ||
| version | Yes | ||
| findings | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / decisaoAdded value: +{
+ "additionalProperties": false,
+ "properties": {
+ "needs": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "rules": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "id": {
+ "type": "string"
+ },
+ "mantenedor": {
+ "additionalProperties": false,
+ "properties": {
+ "registro_ans": {
+ "type": "string"
+ },
+ "tipo": {
+ "enum": [
+ "comunidade",
+ "operadora"
+ ]
+ }
+ },
+ "required": [
+ "tipo"
+ ],
+ "type": "object"
+ },
+ "source": {
+ "additionalProperties": false,
+ "properties": {
+ "acesso": {
+ "type": "string"
+ },
+ "data": {
+ "type": "string"
+ },
+ "official": {
+ "type": "boolean"
+ },
+ "titulo": {
+ "type": "string"
+ },
+ "url": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "url",
+ "titulo",
+ "data",
+ "acesso",
+ "official"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "id",
+ "source",
+ "mantenedor"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "tipo": {
+ "enum": [
+ "aprovar_por_regra",
+ "pendente",
+ "encaminhar_auditor"
+ ]
+ }
+ },
+ "required": [
+ "tipo",
+ "rules",
+ "needs"
+ ],
+ "type": "object"
+}Output schema / properties / findings / items / properties / code / enumPrevious value: -[
- "audit.autorizacao_ausente",
- "audit.autorizacao_vencida",
- "audit.carteirinha_ausente",
- "audit.carteirinha_inativa",
- "audit.carteirinha_vencida",
- "audit.data_ausente",
- "audit.operadora_divergente",
- "audit.procedimento_ausente",
- "audit.procedimento_fora_da_tabela",
- "audit.tabela_fora_de_vigencia",
- "audit.tabela_sem_procedimentos",
- "audit.valor_nao_positivo",
- "guia.carteirinha_ausente",
- "guia.executante_ausente",
- "guia.sequencial",
- "item.valor_divergente",
- "item.valor_zerado",
- "lote.acima_do_teto",
- "lote.caractere_invalido",
- "lote.estrutura",
- "lote.guia_duplicada",
- "lote.hash_divergente",
- "lote.valor_total_geral",
- "lote.vazio",
- "regra.combinacao_proibida",
- "regra.max_itens",
- "regra.obrigatorio",
- "regra.padrao",
- "regra.valores",
- "tuss.fora_de_vigencia",
- "tuss.inexistente",
- "versao.divergente",
- "versao.nao_detectada",
- "versao.nao_suportada",
- "xml.doctype",
- "xml.encoding",
- "xml.malformado",
- "xsd.atributo",
- "xsd.elemento_ausente",
- "xsd.elemento_inesperado",
- "xsd.enumeracao",
- "xsd.outro",
- "xsd.padrao",
- "xsd.tamanho",
- "xsd.tipo"
-]New value: +[
+ "audit.autorizacao_ausente",
+ "audit.autorizacao_vencida",
+ "audit.carteirinha_ausente",
+ "audit.carteirinha_inativa",
+ "audit.carteirinha_vencida",
+ "audit.data_ausente",
+ "audit.operadora_divergente",
+ "audit.procedimento_ausente",
+ "audit.procedimento_fora_da_tabela",
+ "audit.tabela_fora_de_vigencia",
+ "audit.tabela_sem_procedimentos",
+ "audit.valor_nao_positivo",
+ "autorizacao.carteirinha",
+ "autorizacao.dado_ausente",
+ "autorizacao.exige_auditoria",
+ "autorizacao.sem_regra",
+ "guia.carteirinha_ausente",
+ "guia.executante_ausente",
+ "guia.sequencial",
+ "item.valor_divergente",
+ "item.valor_zerado",
+ "lote.acima_do_teto",
+ "lote.caractere_invalido",
+ "lote.estrutura",
+ "lote.guia_duplicada",
+ "lote.hash_divergente",
+ "lote.valor_total_geral",
+ "lote.vazio",
+ "regra.combinacao_proibida",
+ "regra.exige_autorizacao",
+ "regra.max_itens",
+ "regra.obrigatorio",
+ "regra.padrao",
+ "regra.valores",
+ "tuss.fora_de_vigencia",
+ "tuss.inexistente",
+ "versao.divergente",
+ "versao.nao_detectada",
+ "versao.nao_suportada",
+ "xml.doctype",
+ "xml.encoding",
+ "xml.malformado",
+ "xsd.atributo",
+ "xsd.elemento_ausente",
+ "xsd.elemento_inesperado",
+ "xsd.enumeracao",
+ "xsd.outro",
+ "xsd.padrao",
+ "xsd.tamanho",
+ "xsd.tipo"
+]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 implies a non-mutating validation step and clarifies it is not the fix tool, but it does not disclose validation scope, idempotency, permissions, or whether any side effects exist. The usage cycle adds useful context but leaves meaningful behavioral gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with what the tool does, followed by when to use and when not to use it. It is short, structured, and every sentence has a clear purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has five parameters, nested objects, and only 20% schema description coverage, with no annotations. The description covers purpose and usage well but leaves parameter composition and behavioral details incomplete for a tool of this complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 20% across five parameters, and the description mentions only XML and lote input forms. It does not explain data, contexto, operadora, or whether at least one input form is required, so it fails to compensate for the low schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: 'Valida XML TISS ou lote em JSON.' It also distinguishes validation from correction by referencing tiss_apply_fixes in the exclusion guidance, so the agent can separate it from sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says when to use ('antes de gerar ou enviar um lote') and when not to use ('para corrigir achados sem aplicar o ciclo validar → tiss_apply_fixes → validar de novo'), naming the alternative workflow. This is strong routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.