Skip to main content
Glama
mdiaoficial

mdia-feegow-mcp

by mdiaoficial

feegow_list_health_programs

Retrieve registered health programs with pagination and filters by status, dates, program ID, agreement, name, or type.

Instructions

[Pacientes] Lista todos os programas de saúde cadastrados. Para paginar, defina a posição inicial (offset) e o limite de resultados (limit). (HTTP GET /patient/health-programs)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoLimite na quantidade de resultados retornados.
queryNoParâmetros de query adicionais (chave/valor) não listados acima.
offsetNoNúmero de registros a pular na requisição.
statusNoFiltro por status (Ativo = 1, Inativo = 0).
data_endNoFiltro por data final do programa (yyyy-mm-dd).
data_startNoFiltro por data inicial do programa (yyyy-mm-dd).
program_idNoFiltro por id do programa (apenas números).
convenio_idNoFiltro por id do convênio (apenas números).
nome_programaNoFiltro por nome do programa.
tipo_programa_idNoFiltro por id do tipo do programa (apenas números).
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the tool lists health programs, without mentioning if it's read-only, idempotent, or any side effects. Minimal transparency.

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?

Two sentences with no wasted words. Efficiently communicates the core action and pagination. Could benefit from structuring but remains clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is provided, and the description fails to explain the response structure. With 10 parameters and no behavioral details, the description is insufficient for an agent to fully understand the tool's behavior and output.

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 baseline is 3. The description only adds brief mention of offset and limit for pagination, but does not add significant meaning beyond what the schema already provides.

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 'Lista todos os programas de saúde cadastrados' which is a specific verb+resource combination. It also mentions pagination with offset and limit. Among many sibling tools, this is the only one for health programs, so distinction is clear.

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 gives a hint about pagination parameters but provides no explicit guidance on when to use this tool versus alternatives, nor any when-not-to-use conditions. No mention of prerequisites or context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mdiaoficial/mdia-feegow-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server