Check shipping costs for all logistics services in Indonesia.
Scored across 3 tools
Each tool serves a clearly distinct purpose: get_courier_rates for shipping costs, get_map_areas for administrative IDs, and usage_statistic for API limits. There is no overlap or ambiguity between them.
Two tools follow the get_verb_noun pattern (get_courier_rates, get_map_areas), but usage_statistic deviates as a noun phrase. The naming is still readable and predictable, with only a minor inconsistency.
With only 3 tools, the set is well-scoped for a focused logistic rates API. Each tool is necessary, and the count falls comfortably within the typical 3-15 range, avoiding bloat.
The tool surface covers the full workflow: get_map_areas provides required area IDs, get_courier_rates delivers the core functionality, and usage_statistic handles API monitoring. There are no obvious gaps for the stated purpose.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
get_courier_ratesget_map_areasusage_statistic
Add one secure layer between your agents and this server.
