port-emissions-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT_DATA_DIR | No | The folder containing the port tables, if using your own copy or a newer extraction. If not set, the server looks for the dataset downloaded from Zenodo, then falls back to the bundled synthetic dataset. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| estimate_berth_co2A | Estimate the at-berth CO2 of ONE liquid-bulk (tanker) call from the auxiliary engine, i.e. the CO2 that Onshore Power Supply (shore power) would avoid. Boilers are excluded. Args: dwt: deadweight tonnage of the vessel. berth_hours: hours at berth (from berthing to unberthing). fuel: fuel burnt by the auxiliary engine. sfoc_g_per_kwh: specific fuel oil consumption, default 215 g/kWh. |
| estimate_calls_co2A | Estimate at-berth (OPS-avoidable) CO2 for MANY liquid-bulk calls and sum it. Args: calls: list of objects with keys "dwt" and "berth_hours" (optional "call_id"). fuel: fuel burnt by the auxiliary engine. |
| find_installationA | Search Brazilian port installations (public ports and private terminals) by name, port complex or ANTAQ code, e.g. "Itaqui", "Ponta da Madeira", "Paranagua", "BRSSZ". Returns ANTAQ codes to use in the other tools. |
| port_profileA | Year-by-year profile of one installation: cargo handled (tonnes), split by navigation type, number of cargo berthings and mean port times (waiting, operation, at berth). Args: installation: ANTAQ code (e.g. BRIQI) or an unambiguous name. start_year, end_year: period, inclusive (data from 2010). |
| compare_portsA | Compare several installations on one indicator in one year, ranked high to low. Args: installations: ANTAQ codes or unambiguous names. indicator: tonnes, berthings, waiting_hours, hours_at_berth or total_stay_hours. year: reference year. |
| explain_methodB | Explain the method, parameters and sources behind a tool's numbers. |
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
The two estimator tools are distinguished by scale (ONE call vs MANY calls), and port_profile (single installation over time) vs compare_ports (several installations in one year) are clearly differentiated. There is minor overlap in purpose between the two CO2 estimators, but descriptions make the intent clear.
Most tools follow a verb_noun pattern (estimate_berth_co2, estimate_calls_co2, find_installation, compare_ports, explain_method). port_profile deviates from this pattern by using noun_noun, a minor inconsistency.
Six tools is well-scoped for a niche port-emissions analysis domain. Each tool—single estimation, batch estimation, lookup, profile, comparison, and method explanation—earns its place without redundancy.
The surface covers the core lifecycle: finding installations, profiling, comparing, estimating emissions, and explaining methods. Minor gaps exist, such as no direct tool to enumerate all installations or aggregate multi-year comparisons, but agents can work around these.