Skip to main content
Glama

Feegow Clinic

by io.github.mcp-dir

feegow_patient_list

Read-onlyIdempotent

Read patients in Feegow Clinic. Actions:

  • list: paginated patient list (offset/limit). Filter by telefone, cpf, origem_id, alterado_em, data_aniversario.

  • get: full detail by paciente_id (includes address, insurance, documents).

  • search_cpf: find patient by CPF (11 digits, numbers only). Returns name, birth date, gender, address, phones, emails, documents, insurance info.

[Flattened action: list]

Bulk support: accepts paciente_ids, origem_ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cpfNo
limitNo
photoNo
offsetNo
accountNo
telefoneNo
origem_idNo
origem_idsNo
alterado_emNo
paciente_idNo
paciente_idsNo
programa_saudeNo
data_aniversarioNo

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds that it reads patients, supports bulk arrays, and returns specific fields. Does not contradict annotations, but adds only moderate value beyond them.

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?

Structured with bullet points for actions, but includes redundant mention of return fields twice. Some extra verbiage like '[Flattened action: list]' may confuse. Could be trimmed without losing meaning.

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

Completeness3/5

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

No output schema, 13 params, no param descriptions in schema. Description explains the three modes and bulk, but lacks guidance on parameter conflicts (e.g., using paciente_id and cpf together) and error behavior. Adequate but not thorough.

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 coverage 0%, so description must compensate. It explains some parameters: offset/limit for pagination, filter fields (telefone, cpf, etc.), CPF format, bulk arrays. However, it omits photo, account, programa_saude. Partially covers the 13 parameters, enough to guide basic usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Describes multiple read actions (list, get, search_cpf) clearly with specific verb and resource. However, does not differentiate from sibling tools like feegow_patient_get and feegow_patient_search_cpf, which likely serve the same single operations. Sibling differentiation is missing.

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?

Implied usage: use list for paginated queries, get for full detail, search_cpf for CPF lookup. But no explicit guidelines on when to use this combined tool versus separate sibling tools. No exclusions or alternatives mentioned.

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

All Feegow Clinic toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

D1.9/5.0
Disambiguation1/5

Many tools have identical descriptions (e.g., multiple tools with same 'Read appointments and scheduling data' text) and only differ by a 'flattened action' label, making it impossible for an agent to distinguish which tool to call for a specific operation.

Naming Consistency2/5

Names follow a loose verb_noun pattern but are extremely inconsistent: some use underscores, some have redundant prefixes like 'feegow_appointment_', and the same actions are duplicated across multiple tool names (e.g., 'list' appears in many). The 'flattened action' suffix is confusing.

Tool Count1/5

94 tools is far too many for a clinic management system. This is clearly due to a one-action-per-tool design that fragments the API surface, making the server bloated and hard to navigate. A typical well-structured server for this domain would have 10-20 tools.

Completeness3/5

The server covers many areas (appointments, patients, financial, procedures, stock, etc.), suggesting broad functionality. However, the fragmentation obscures gaps and makes it difficult to determine if all CRUD operations exist for each entity. Some areas (e.g., stock write) have multiple tools for single actions.

Resources