mcp-comexstat
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMEXSTAT_API_URL | No | Base URL of the API | https://api-comexstat.mdic.gov.br |
| COMEXSTAT_TIMEOUT_MS | No | Maximum timeout per request in milliseconds | 30000 |
| COMEXSTAT_MAX_RETRIES | No | Maximum number of retry attempts | 4 |
| COMEXSTAT_CACHE_TTL_MS | No | Cache TTL in milliseconds | 300000 |
| COMEXSTAT_RETRY_BASE_DELAY_MS | No | Initial delay for exponential backoff in milliseconds | 1000 |
| COMEXSTAT_MIN_REQUEST_INTERVAL_MS | No | Minimum interval between requests in milliseconds | 500 |
| COMEXSTAT_QUERY_MIN_REQUEST_INTERVAL_MS | No | Minimum interval between data queries in milliseconds | 10000 |
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
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 20 tools
Most tools have clearly distinct purposes targeting different data entities (countries, states, cities, NBM, etc.) or metadata (available fields, filters, metrics). However, some pairs like getCities/getMunicipalitiesData and getNBM/getNBMDetails have potential overlap that could cause confusion without descriptions to clarify their boundaries.
All tool names follow a consistent verb_noun pattern with 'get' or 'query' prefixes, using camelCase uniformly throughout. The naming is highly predictable and readable, with clear conventions for different types of operations (get for metadata/entities, query for data retrieval).
With 20 tools, this is borderline heavy for a trade statistics server. While the domain appears broad (covering countries, states, cities, NBM codes, auxiliary tables, etc.), the count feels somewhat inflated with multiple similar metadata tools (getAvailableFields/Filters/Metrics/Years) that might be consolidated.
The tool set appears to provide comprehensive coverage for trade data exploration and retrieval, including metadata discovery, entity lookups, and data querying across different dimensions (current, historical, municipal). Minor gaps might exist in data modification capabilities, but for a read-only statistical service, the surface seems reasonably complete.