Skip to main content
Glama
ThiagoJacobLannes

brasil-planos-saude-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BRASIL_PLANOS_SAUDE_CACHE_DIRNoSet to use another folder for the cache.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
find_operatorsA

Find Brazilian health-plan operators (operadoras de planos de saúde) registered with ANS.

Use it to turn a brand the user mentions ("Unimed BH", "Amil", "Bradesco Saúde") into the ANS registry number, or to list operators by state, city or type. Largest first.

Args: query: Part of the name, the CNPJ, or the ANS registry number. Accents and case don't matter. Several words must all match ("unimed campinas"). uf: State of the operator's head office, e.g. "SP", "MG". city: City of the head office, e.g. "Belo Horizonte". modality: e.g. "Cooperativa Médica", "Medicina de Grupo", "Seguradora", "Autogestão", "Odontologia de Grupo", "Filantropia", "Administradora de Benefícios" (substring match). include_cancelled: Also list operators whose registration was cancelled. limit: How many to return (default 10, max 50).

Each operator: registro_ans, name, legal name, modality, head office, status, and beneficiaries and size class (porte) per coverage. Head office is not where the operator sells plans.

operator_profileA

Everything ANS publishes about one health-plan operator, to judge whether it is a good choice.

Use for "is Hapvida good?", "how does Unimed Campinas rank on complaints?", "has SulAmérica been fined?". Returns:

  • registration: legal name, CNPJ, modality, head office, phone, status (active or cancelled, with date and reason), beneficiaries and size class;

  • complaints (IGR): latest month, 12-month average, the median of operators of the same size, the operator's position among them, and the monthly series;

  • quality (IDSS, 0-1, higher is better) for the last 5 years with its four dimensions;

  • access-to-care monitoring band (0 best, 3 worst) for the last published quarters;

  • fines applied by ANS: totals, last 5 years, status and the most recent cases;

  • the readjustment applied to its small-group pool (contracts with < 30 lives).

Args: operator: Name (or part of it), CNPJ, or ANS registry number. If the name matches several operators, the largest active one is used and the others are listed in outras_operadoras_com_nome_parecido: check it is the one the user meant (Unimed, for example, is hundreds of separate cooperatives). coverage: "medica" or "odonto". Default: every coverage the operator has.

Always quote the month/year of each figure and explain that IGR is lower-is-better and IDSS higher-is-better (see como_ler in the result).

compare_operatorsA

Side-by-side comparison of 2 to 8 health-plan operators on the ANS indicators.

Use for "Amil or Bradesco Saúde?", "compare the plans my company offers". For each operator: 12-month complaints index (IGR) with the median of its size class and its position, latest IDSS, latest access-to-care band, number of fines in the last 5 years, and the latest small-group readjustment.

Args: operators: Names, CNPJs or ANS registry numbers, e.g. ["Amil", "Bradesco Saúde", "SulAmérica"]. coverage: "medica" (default) or "odonto".

rank_operatorsA

Rank active health-plan operators by complaints or by quality.

Use for "which large health plans get the fewest complaints?", "best-rated dental plans", "worst operators in Minas Gerais".

Args: by: "reclamacoes" (12-month IGR, lower is better) or "qualidade" (latest IDSS, higher is better). coverage: "medica" (default) or "odonto". porte: "pequeno" (< 20k beneficiaries), "medio" (20k-100k) or "grande" (> 100k). ANS itself only compares operators of the same size. uf: Head-office state, e.g. "MG". Not the same as where it sells plans. modality: e.g. "Cooperativa Médica", "Medicina de Grupo", "Seguradora". min_beneficiaries: Skip operators smaller than this (default 5000; tiny ones swing wildly). worst_first: True to list the worst first. limit: How many to return (default 10, max 50).

where_to_complainA

How to complain about a health plan in Brazil: the official ANS channels and the steps.

Use when a user's plan denied or delayed a procedure, or they have a contract problem. Each channel was checked on the ANS consumer-service page (conferido_em).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct task: single-operator deep lookup, operator discovery/search, multi-operator comparison, ranked lists, and complaint-channel guidance. The boundaries are reinforced by clear use-case examples in the descriptions, so an agent can reliably choose the right tool. There is minor overlap between find/compare/rank because all involve operators, but their purposes and outputs are sharply differentiated.

Naming Consistency4/5

Most names follow a clear verb_noun or action pattern: find_operators, compare_operators, rank_operators. operator_profile is noun-based and where_to_complain is a phrase, which are minor deviations but still readable and intuitive. The overall set is consistent enough to predict tool behavior.

Tool Count5/5

Five tools is well-scoped for a focused domain of Brazilian health-plan operator data and consumer guidance. Each tool earns its place: search, profile, comparison, ranking, and complaint routing. There is no obvious redundancy or missing major workflow.

Completeness4/5

The surface covers discovery, detailed profile retrieval, comparison, ranking, and complaint guidance, which addresses the core informational needs of the domain. Minor gaps might include a dedicated tool for plan/product-level details or direct access to underlying time-series data, but these are workable through operator_profile. The read-only nature of the server makes CRUD lifecycle coverage less relevant.

Maintenance

ActivityMaintained
ResponsivenessNo issues