Skip to main content
Glama

Mestre Prático • Brazil Retail & Commodities MCP

by io.github.arthursantosmedia-stack
OverviewDiscussionsAdmin

brazil_freight_logistics

Read-onlyIdempotent

Calculates official Brazilian minimum road freight rates regulated by ANTT (Agencia Nacional de Transportes Terrestres - Resolution No. 5,867/2020) across all vehicle classes (2 to 9 axles) and cargo types (solid bulk, general cargo, refrigerated). Correlates freight costs with ANP Diesel S10 pump prices, computing diesel fuel expense ratio and the logistical cost impact per kilogram of food transported. When to use: Calculate official ANTT freight rates, diesel expense ratio, or transport logistics costs between Brazilian cities. When NOT to use: Do NOT use for retail diesel pump prices at local gas stations (use brazil_fuel_prices). Read-only and idempotent operation; zero authentication required.

Input Schema

NameRequiredDescriptionDefault
uf_origemNoOrigin state code (e.g., 'sp', 'rj', 'mg') for diesel price correlation. Defaults to 'sp'.sp
tipo_cargaNoANTT cargo classification type. Defaults to 'geral'.geral
uf_destinoNoTwo-letter Brazilian state acronym for destination (e.g., 'rj', 'sp', 'mg', 'ba'). Defaults to 'rj'.rj
distancia_kmYesTotal road route distance in kilometers (e.g., 430 for SP-RJ corridor). Defaults to 100 km.
numero_eixosNoNumber of vehicle axles: 2 (Toco 8t), 3 (Truck 14t), 4 (Cavalo Toco 22t), 5 (Carreta 27t), 6 (Carreta 32t), 7 (Bitrem 38t), 9 (Rodotrem 50t). Defaults to 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / distancia_km / minimum
      Removed value: -1
    • changedInput schema / properties / numero_eixos / description
      Previous value: -"Number of vehicle axles: 2 (Toco 8t), 3 (Truck 14t), 4 (Cavalo Toco 22t), 5 (Carreta 27t), 6 (Carreta 32t), 7 (Bitrem 38t), 9 (Rodotrem 50t). Defaults to 3."New value: +"Number of vehicle axles: 2 (Toco 8t), 3 (Truck 14t), 4 (Cavalo Toco 22t), 5 (Carreta 27t), 6 (Carreta 32t), 7 (Bitrem 38t), 9 (Rodotrem 50t). Defaults to 5."
  2. Changed2 schema fields changed
    • addedInput schema / properties / distancia_km / minimum
      Added value: +1
    • changedInput schema / properties / numero_eixos / description
      Previous value: -"Number of vehicle axles: 2 (Toco 8t), 3 (Truck 14t), 4 (Cavalo Toco 22t), 5 (Carreta 27t), 6 (Carreta 32t), 7 (Bitrem 38t), 9 (Rodotrem 50t). Defaults to 5."New value: +"Number of vehicle axles: 2 (Toco 8t), 3 (Truck 14t), 4 (Cavalo Toco 22t), 5 (Carreta 27t), 6 (Carreta 32t), 7 (Bitrem 38t), 9 (Rodotrem 50t). Defaults to 3."
  3. Changed2 schema fields changed
    • changedInput schema / properties / numero_eixos / description
      Previous value: -"Vehicle axle configuration (2=truck, 3=heavy truck, 5=semi-trailer, 6=trailer, 7=bitrem, 9=rodotrem). Defaults to 3."New value: +"Number of vehicle axles: 2 (Toco 8t), 3 (Truck 14t), 4 (Cavalo Toco 22t), 5 (Carreta 27t), 6 (Carreta 32t), 7 (Bitrem 38t), 9 (Rodotrem 50t). Defaults to 5."
    • addedInput schema / properties / uf_destino
      Added value: +{
+  "default": "rj",
+  "description": "Two-letter Brazilian state acronym for destination (e.g., 'rj', 'sp', 'mg', 'ba'). Defaults to 'rj'.",
+  "type": "string"
+}
  4. Changed11 schema fields changed
    • addedInput schema / properties / distancia_km / default
      Added value: +100
    • changedInput schema / properties / distancia_km / description
      Previous value: -"Highway route distance in kilometers. Defaults to 450 km (e.g. SP-RJ axis or regional agricultural corridor) if omitted."New value: +"Total road route distance in kilometers (e.g., 430 for SP-RJ corridor). Defaults to 100 km."
    • addedInput schema / properties / numero_eixos
      Added value: +{
+  "default": 3,
+  "description": "Vehicle axle configuration (2=truck, 3=heavy truck, 5=semi-trailer, 6=trailer, 7=bitrem, 9=rodotrem). Defaults to 3.",
+  "enum": [
+    2,
+    3,
+    4,
+    5,
+    6,
+    7,
+    9
+  ],
+  "type": "integer"
+}
    • addedInput schema / properties / tipo_carga / default
      Added value: +"geral"
    • changedInput schema / properties / tipo_carga / description
      Previous value: -"Cargo classification per ANTT: 'granel_solido' (grains/staples), 'carga_geral' (packaged groceries), 'frigorificada' (meats/dairy). Defaults to 'granel_solido'."New value: +"ANTT cargo classification type. Defaults to 'geral'."
    • changedInput schema / properties / tipo_carga / enum
      Previous value: -[
-  "granel_solido",
-  "carga_geral",
-  "frigorificada",
-  "perigosa"
-]New value: +[
+  "geral",
+  "granel_solido",
+  "granel_liquido",
+  "frigorificada",
+  "perigosa"
+]
    • removedInput schema / properties / tipo_veiculo
      Removed value: -{
-  "description": "Truck axle configuration: 'carreta_5_eixos' (standard 27t), 'truck_3_eixos' (14t), 'bitrem_7_eixos' (38t), or 'rodotrem_9_eixos' (50t grain hauler). Defaults to 'carreta_5_eixos'.",
-  "enum": [
-    "toce_2_eixos",
-    "truck_3_eixos",
-    "cavalo_toco_4_eixos",
-    "carreta_5_eixos",
-    "bitrem_7_eixos",
-    "rodotrem_9_eixos"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / uf_destino
      Removed value: -{
-  "description": "Two-letter state acronym of cargo destination (e.g. 'RJ', 'SP', 'BA'). Defaults to 'RJ'.",
-  "type": "string"
-}
    • addedInput schema / properties / uf_origem / default
      Added value: +"sp"
    • changedInput schema / properties / uf_origem / description
      Previous value: -"Two-letter state acronym of cargo origin (e.g. 'MT', 'PR', 'SP'). Defaults to 'SP'."New value: +"Origin state code (e.g., 'sp', 'rj', 'mg') for diesel price correlation. Defaults to 'sp'."
    • addedInput schema / required
      Added value: +[
+  "distancia_km"
+]
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, and the description avoids repeating them wholesale while adding that zero authentication is required — context not present in the annotations. It also discloses the regulatory basis (Resolution 5,867/2020) and the correlation behavior with ANP Diesel S10 prices. It does not describe the shape of the computed result, which leaves a modest gap.

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?

Front-loaded with the core computation before the usage rules, and every sentence carries information (scope, regulatory source, usage routing, safety profile). Slightly dense with the parenthetical agency expansion, but no padding.

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?

With no output schema, the description does carry the burden of return-value disclosure, and it names the outputs it computes (freight rate, diesel fuel expense ratio, cost impact per kg). This is enough for an agent to know what to expect, though the exact result fields and units are not enumerated.

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 parameters are already fully documented including enums and defaults, making 3 the baseline. The description restates axle range (2-9) and cargo categories that already exist in the schema, and only lightly signals that origin/destination states drive the diesel price correlation.

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?

States a specific verb and resource ('Calculates official Brazilian minimum road freight rates regulated by ANTT') and scopes it precisely to vehicle classes and cargo types. This is clearly separable from every sibling, and it explicitly names brazil_fuel_prices as the tool it is not.

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

Usage Guidelines5/5

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

Contains an explicit 'When to use' clause listing the three computations (ANTT rates, diesel expense ratio, logistics costs between cities) and a 'When NOT to use' clause routing retail diesel queries to brazil_fuel_prices. Both the positive and negative conditions are stated.

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

All Mestre Prático • Brazil Retail & Commodities MCP toolsInspect
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