Skip to main content
Glama

Mestre Prático • Brazil Retail & Commodities MCP

by io.github.arthursantosmedia-stack
OverviewDiscussionsAdmin

brazil_contract_intent_a2a

Idempotent

Issues a cryptographically signed Machine-to-Machine (A2A) Economic Intent Protocol and settlement guarantee. Enables enterprise autonomous agents (fleet management bots, hospital procurement systems, wholesale supply coordinators) to formalize an intention to acquire fuels, basic food baskets, or regulated pharmaceutical supplies. The oracle verifies factual minimum prices against primary audited databases and generates a tamper-proof SHA-256 digital certificate issued by TECNOLOGIA E INTELIGÊNCIA DE VAREJO INOVA SIMPLES I.S., valid for 24 hours as an immutable settlement ceiling. When to use: Use when two autonomous agents need to negotiate and seal a formal procurement protocol with verifiable digital signature and settlement bounds. When NOT to use: Do NOT use for simple read-only price checks (use brazil_fuel_prices, brazil_grocery_basket, or brazil_pharma_medicines). Idempotent cryptographic certificate generation.

Input Schema

NameRequiredDescriptionDefault
ufYesTwo-letter Brazilian state code where procurement will take place (e.g., 'rj', 'sp', 'mg', 'ba', 'pe'). Defaults to 'rj'.rj
cidadeNoTarget Brazilian municipality or distribution hub (e.g., 'Cabo Frio', 'Sao Paulo', 'Recife', 'Rio de Janeiro'). Defaults to 'Cabo Frio'.Cabo Frio
tipo_operacaoYesEconomic procurement category for the machine intent contract: 'abastecimento_frota' (fleet refueling), 'cesta_basica_atacado' (wholesale food baskets), 'dispensacao_farmaceutica' (pharmaceutical supply), 'auditoria_tributaria' (tax audit certification). Defaults to 'abastecimento_frota'.abastecimento_frota
item_especificoNoSpecific commodity code, fuel type (e.g., 'diesel_s10', 'gasolina'), or active pharmaceutical ingredient (e.g., 'losartana'). Defaults to 'diesel_s10'.diesel_s10
volume_estimadoNoEstimated procurement volume in liters (for fuels), units (for food baskets), or packages (for medicines). Defaults to 500.
agente_solicitante_idNoUnique identifier or public key of the requesting partner AI agent or automated fleet bot. Defaults to 'FleetBot-Logistica-01'.FleetBot-Logistica-01

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / uf / enum
      Removed value: -[
-  "ac",
-  "al",
-  "am",
-  "ap",
-  "ba",
-  "ce",
-  "df",
-  "es",
-  "go",
-  "ma",
-  "mg",
-  "ms",
-  "mt",
-  "pa",
-  "pb",
-  "pe",
-  "pi",
-  "pr",
-  "rj",
-  "rn",
-  "ro",
-  "rr",
-  "rs",
-  "sc",
-  "se",
-  "sp",
-  "to"
-]
    • removedInput schema / properties / volume_estimado / minimum
      Removed value: -1
  2. Changed2 schema fields changed
    • addedInput schema / properties / uf / enum
      Added value: +[
+  "ac",
+  "al",
+  "am",
+  "ap",
+  "ba",
+  "ce",
+  "df",
+  "es",
+  "go",
+  "ma",
+  "mg",
+  "ms",
+  "mt",
+  "pa",
+  "pb",
+  "pe",
+  "pi",
+  "pr",
+  "rj",
+  "rn",
+  "ro",
+  "rr",
+  "rs",
+  "sc",
+  "se",
+  "sp",
+  "to"
+]
    • addedInput schema / properties / volume_estimado / minimum
      Added value: +1
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true), so the lower bar applies. The description still adds real context: an oracle verification step against audited databases, a SHA-256 certificate with a named issuer, and a 24-hour validity as an immutable settlement ceiling. It does not mention authentication prerequisites, failure modes, or rate limits, which keeps it below a 5.

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

Conciseness3/5

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

The when/when-not routing is front-loaded and useful, but the prose is padded with promotional phrasing ('tamper-proof', the full corporate name, 'Idempotent cryptographic certificate generation' which restates the annotation). Several clauses could be pruned without losing guidance.

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?

There is no output schema, and the description compensates by explaining the artifact produced (signed certificate, validity window, settlement ceiling) so an agent knows what to expect back. With only two required parameters and full schema coverage, the remaining gap is minor: no statement of what happens on verification failure or what permissions the caller needs.

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 enum values and defaults are already fully documented structurally. The description only loosely maps to parameters via the fuel/food/pharma categories and adds no format or constraint detail beyond the schema. Baseline 3 applies.

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 states a specific verb and artifact ('Issues a cryptographically signed A2A Economic Intent Protocol and settlement guarantee') and immediately narrows the domain to fuels, food baskets, and pharma supplies. An agent can distinguish this from brazil_fuel_prices or brazil_pharma_medicines without inspecting any schema.

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?

Explicit 'When to use' (two autonomous agents sealing a formal procurement protocol with signature and settlement bounds) and 'When NOT to use' naming three specific sibling tools for read-only price checks. Both the positive trigger and the exclusion are spelled out.

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