Skip to main content
Glama
wendellbigato

MCP-CEP

by wendellbigato
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
echoB

Repete o texto enviado.

buscar_cepB

Consulta informações de um CEP brasileiro usando a API ViaCEP.

Args:
    cep: Código de Endereçamento Postal no formato 01001000 ou 01001-000.

Returns:
    Um dicionário com informações de endereço como rua, bairro, cidade e estado.
buscar_ceps_por_logradouroA

Busca todos os CEPs associados a um logradouro em uma cidade e estado.

Args:
    uf: Sigla do estado (ex: SP, RJ)
    cidade: Nome da cidade (ex: São Paulo)
    logradouro: Nome da rua, avenida, praça etc (ex: Praça da Sé)

Returns:
    Lista de dicionários com endereços que correspondem à busca.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored across 3 tools

Disambiguation4/5

The first two tools have clearly distinct purposes: buscar_cep queries by CEP number, while buscar_ceps_por_logradouro queries by address components. However, the echo tool is completely unrelated to the CEP domain, creating a minor ambiguity about the server's primary focus. The core CEP tools are well-differentiated.

Naming Consistency3/5

Two tools follow a consistent Portuguese verb_noun pattern (buscar_cep, buscar_ceps_por_logradouro), but the third tool (echo) breaks this pattern with an English name. The naming is readable but lacks full consistency across the set due to the language and pattern mismatch.

Tool Count3/5

Three tools is borderline for a CEP server. While the two core CEP tools provide basic lookup functionality, the inclusion of an unrelated echo tool makes the count feel artificially inflated. For a focused CEP service, 2-4 domain-specific tools would be more appropriate.

Completeness3/5

The server covers the essential CEP lookup operations: query by CEP and query by address components. However, there are notable gaps for a complete CEP service - no tools for address validation, reverse geocoding, or handling CEP ranges. The echo tool adds no value to the CEP domain coverage.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources