Skip to main content
Glama
marqprochat

personaleasy-mcp-server

by marqprochat

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoPort for the HTTP server3000
MCP_AUTH_TOKENNoBearer token required for the /mcp endpoint when using HTTP mode
PERSONALEASY_API_KEYYesAPI key for the PersonalEasy API (header x-api-key)
PERSONALEASY_BASE_URLNoBase URL for the PersonalEasy APIhttps://prsrb.onrender.com/v1/rpc
PERSONALEASY_CLIENT_IDYesClient ID for the PersonalEasy API

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
personaleasy_get_agendamentosA

Retorna os agendamentos no período informado. Opcionalmente filtra por unidade de atendimento (use personaleasy_get_unidades para descobrir os nomes válidos).

personaleasy_get_kpi_producaoA

Retorna dados de produção (KPIs de dashboard) no período informado. Filtros opcionais por unidade e por prestador.

personaleasy_get_prestador_por_cpfA

Retorna o ID e o Nome do prestador a partir do CPF.

personaleasy_get_unidadesA

Retorna o ID e o Nome das unidades de atendimento ativas.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct resource: appointments (agendamentos), production KPIs, provider lookup by CPF, and units. There is no overlap in purpose, and the descriptions clearly differentiate them.

Naming Consistency4/5

All tools follow the pattern `personaleasy_get_<resource>`, using the same prefix and verb. The resource names are in Portuguese, which is consistent with the domain, though the prefix adds redundancy.

Tool Count4/5

Four tools is appropriate for a focused server that provides read-only access to core entities (appointments, KPIs, providers, units). It is not too few for the apparent scope, and each tool serves a clear purpose.

Completeness3/5

The tool set covers reading key entities, but there are obvious gaps: no filtering by provider for appointments, no tool for patients or procedures, and only a CPF-based lookup for providers. Write operations (create, update, delete) are absent, limiting the surface to querying.

Maintenance

ActivitySlowing
ResponsivenessNo issues