Portuguese Competition 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pt_comp_search_decisionsA | Full-text search across AdC (Autoridade da Concorrencia) enforcement decisions (abuse of dominance, cartel, sector inquiries). Returns matching decisions with case number, parties, outcome, fine amount, and Lei da Concorrencia articles cited. |
| pt_comp_get_decisionA | Get a specific AdC decision by case number (e.g., 'PRC/2023/1', 'Ccent/2022/5'). |
| pt_comp_search_mergersA | Search AdC merger control decisions (concentracoes de empresas). Returns merger cases with acquiring party, target, sector, and outcome. |
| pt_comp_get_mergerA | Get a specific AdC merger control decision by case number. |
| pt_comp_list_sectorsA | List all sectors with AdC enforcement activity, including decision counts and merger counts per sector. |
| pt_comp_aboutA | Return metadata about this MCP server: version, data source, coverage, and tool list. |
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 6 tools
Each tool has a clearly distinct purpose: search vs. get, decisions vs. mergers, plus aggregate sector info and metadata. No two tools overlap in functionality or intended use.
The consistent pt_comp_ prefix and verb_noun pattern (search_decisions, get_decision, search_mergers, get_merger, list_sectors) make naming predictable. The 'about' tool breaks the verb_noun pattern slightly, and there's a minor singular/plural mismatch between search and get, but these are trivial.
Six tools is an appropriate scope for a focused competition law database: two resource types each with search and get, plus a sector overview and server metadata. Nothing feels redundant or missing.
For a read-only legal information server, the surface is complete: it offers both search and retrieval for the two core entity types (decisions and mergers), and list_sectors provides useful aggregate context. No dead ends or essential missing operations.