Oráculo B2R

by dev.workers.rendercriativo.oraculo-b2r

Calcular Fator R (Simples Nacional)

calculate_fator_r

Read-onlyIdempotent

Calcula o Fator R do Simples Nacional (Art. 18, § 5º-J da LC 123/2006) com inteligência tributária avançada. Suporta validação automática de CNAE, proporcionalização de receitas/folha para empresas com menos de 12 meses de atividade, e projeções de cenários futuros de crescimento.

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": {
      "rbt12": "<rbt12>",
      "folha12": "<folha12>"
    },
    "name": "calculate_fator_r"
  }
}

Input Schema

Name	Required	Description
`cnae`	No	Código CNAE principal da empresa (opcional, ex: "6201-5/01" para desenvolvimento de software)
`rbt12`	Yes	Receita Bruta Total acumulada nos últimos 12 meses em R$ (ex: 360000)
`folha12`	Yes	Folha de pagamento acumulada nos últimos 12 meses em R$ (inclui pró-labore dos sócios e salários + INSS)
`faturamento_mes`	No	Faturamento em R$ do mês atual a ser tributado (opcional)
`meses_atividade`	No	Quantidade de meses de atividade da empresa se tiver menos de 12 meses (opcional, ex: 6 para proporcionalizar RBT12/Folha12)
`projecao_crescimento_pct`	No	Percentual estimado de crescimento do faturamento mensal nos próximos meses (opcional, ex: 20 para 20%)

Output Schema

Name	Required	Description	Default
`content`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "content": {
+      "items": {
+        "properties": {
+          "text": {
+            "description": "JSON serializado com o cálculo detalhado do Fator R",
+            "type": "string"
+          },
+          "type": {
+            "description": "Tipo do conteúdo (ex: \"text\")",
+            "type": "string"
+          }
+        },
+        "required": [
+          "type",
+          "text"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "content"
+  ],
+  "type": "object"
+}

First observedJul 21, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral traits beyond annotations, such as automatic CNAE validation, proportionalization for companies with less than 12 months, and projection of future growth scenarios. These are useful context that annotations lack.

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 description consists of two sentences. The first sentence states the purpose and legal reference, while the second lists key features. It is concise and front-loaded, but the features list could be more integrated. Overall, it earns its place without unnecessary verbosity.

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 the tool's complexity (6 parameters, 2 required, 100% schema coverage, and an output schema exists), the description covers the main aspects: purpose, legal basis, and advanced features. It does not explain return values, but the output schema presumably handles that. No major gaps for a calculator tool.

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%, with each parameter clearly described (e.g., rbt12: 'Receita Bruta Total acumulada nos últimos 12 meses em R$'). The description does not add significant detail beyond the schema, only mentioning the tool's 'advanced tax intelligence' and listing features. No contradiction or missing semantics noted.

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 clearly states the tool calculates the Fator R for Simples Nacional with a specific legal reference (Art. 18, § 5º-J da LC 123/2006) and mentions advanced features. It distinguishes itself from sibling tools like fetch_oracle_data, query_export_rules, and simulate_simples_nacional by focusing on calculation rather than data retrieval or simulation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives. It lists features but does not specify prerequisites, when it is appropriate, or when not to use it. Sibling tools are not compared or excluded.

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

All Oráculo B2R tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?