Brazilian CEP MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Name | Description |
|---|---|
| consultar-cepA | Query address information from a Brazilian postal code (CEP) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined and singular.
Since there is only one tool, naming consistency is inherently perfect, as there are no other tool names to compare it against for patterns or conventions.
A single tool for a CEP lookup server feels thin and under-scoped, as it only provides query functionality without supporting related operations like validation, batch processing, or reverse lookup. This limits the server's utility for broader agent workflows.
The server is severely incomplete for a CEP domain, as it only offers a query tool without any complementary operations such as address validation, error handling for invalid CEPs, or integration with other Brazilian address services, leaving significant gaps in functionality.