Skip to main content
Glama
Mestre Prático & NutriPreço Official MCP Server

Mestre Prático & NutriPreço Official MCP Server

brazil_pharma_medicines

Read-onlyIdempotent

Query official Brazilian regulated medicine price ceilings (PMC) and factory prices (PF) from CMED/ANVISA by brand or active ingredient, including state ICMS rates and Farmácia Popular eligibility.

Instructions

Queries official Maximum Consumer Prices (PMC) and Factory Prices (PF) for 26,635+ regulated medicines in Brazil from CMED/ANVISA, including state-specific ICMS tax brackets (18% to 20%), active ingredients, laboratory, presentation, and free eligibility under the federal Farmacia Popular program. Updated monthly per CMED resolution. Read-only operation; no authentication required up to 60 req/min (returns up to 15 matching presentations per call).

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": {
      "termo": "<termo>"
    },
    "name": "brazil_pharma_medicines"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufNoTwo-letter Brazilian state code (e.g., 'sp', 'rj', 'mg') to apply accurate regional ICMS tax rate (default: 'sp').
tipoNoRegulatory category filter (default: 'todos').
termoYesCommercial brand name or active ingredient in Portuguese (e.g., 'dipirona', 'losartana', 'ozempic', 'amoxicilina', 'paracetamol').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / termo / description
      Previous value: -"Nome comercial ou princípio ativo do medicamento (ex: 'dipirona', 'losartana', 'ozempic', 'amoxicilina', 'paracetamol')"New value: +"Commercial brand name or active ingredient in Portuguese (e.g., 'dipirona', 'losartana', 'ozempic', 'amoxicilina', 'paracetamol')."
    • changedInput schema / properties / tipo / description
      Previous value: -"Filtro por tipo de produto regulatório"New value: +"Regulatory category filter (default: 'todos')."
    • changedInput schema / properties / uf / description
      Previous value: -"Sigla do estado brasileiro (ex: 'sp', 'rj', 'mg') para alíquota de ICMS regional (padrão: 'sp')"New value: +"Two-letter Brazilian state code (e.g., 'sp', 'rj', 'mg') to apply accurate regional ICMS tax rate (default: 'sp')."
  2. First observedv1.0.0

TDQS

A3.9/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 openWorld behavior. The description adds meaningful operational context beyond annotations: no authentication required, a 60 req/min limit, monthly CMED updates, and a cap of 15 matching presentations per call. It does not explain pagination or no-result behavior, so it is not fully complete.

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 is front-loaded with the core resource and scope, followed by operational limits. It is fairly dense in the first sentence but contains no obvious filler, and every sentence contributes useful information.

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?

For a read-only lookup with fully documented parameters and rich annotations, the description covers the data source, update cadence, rate limit, return cap, and included fields. It leaves pagination and exact no-match behavior unspecified, but overall it is sufficiently complete for correct invocation.

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 all three parameters documented, including defaults, examples, and an enum. The description adds domain context but no parameter-specific meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 ('Queries') and resource ('official Maximum Consumer Prices (PMC) and Factory Prices (PF) for ... regulated medicines in Brazil from CMED/ANVISA'), plus scope and included fields. This clearly distinguishes it from sibling fuel, grocery, LPG, cost-of-living, and regional comparison tools by domain.

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

Usage Guidelines3/5

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

Usage is implied by the medicine-price domain, but the description does not explicitly say when to use this tool versus sibling tools or when not to use it. It lacks named alternatives or exclusion conditions.

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