@cargoffer/zbe-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZBE_API_KEY | Yes | API key for authentication | |
| ZBE_API_URL | No | ZBE API base URL | https://zbe.transcend.cargoffer.com/api |
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 |
|---|---|
| zbe.checkRouteA | Check if a vehicle route intersects Low Emission Zones (ZBE/LEZ) in Spain/Portugal. Use this when you need to know if a truck route passes through restricted urban areas. The API compares the vehicle's Euro emission class with each ZBE's minimum requirement. Returns which ZBEs are intersected and whether the vehicle is restricted from entering. |
| zbe.listPolygonsA | List Low Emission Zone polygons with optional filters. Use this to browse available ZBEs, get their geometries, and see restriction details per city. |
| zbe.getStatsA | Get coverage statistics for the ZBE database. Returns total count, breakdown by country, and last update timestamp. |
| zbe.getBadgeInfoA | Get information about DGT environmental badges (Distintivo Ambiental). Explains what each badge means, which vehicles qualify, and restrictions for each badge type. |
| zbe.getVehicleRestrictionsA | Get specific vehicle access restrictions for a given city's ZBE. Useful when planning routes to understand what vehicles are allowed in each urban area. |
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 5 tools
Each tool has a clear, distinct purpose: route checking, badge info, stats, city restrictions, and polygon listing. No overlap or ambiguity.
All tools follow a consistent camelCase verb_noun pattern (e.g., checkRoute, listPolygons), making them predictable and easy to understand.
Five tools is ideal for this domain, covering key operations without being too sparse or excessive. Each tool earns its place.
The tool set provides complete read-only coverage for querying ZBE data: route checking, city restrictions, polygon browsing, badge explanations, and database stats. No obvious gaps.