balad-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BALAD_MCP_PROXY | No | Optional HTTP proxy URL for the Balad requests; system proxy settings are ignored. A comma-separated list is used one at a time: the next proxy takes over when one is blocked or cannot connect |
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 |
|---|---|
| bl_searchA | Search Balad (Iranian map) for places, streets, neighbourhoods and cities by name, with coordinates and address. Use it to find a specific place or to turn an address or city name into coordinates (geocoding). Results near
the given point rank first, so pass lat/lng (e.g. a city's coordinates from a first bl_search) when searching
outside Tehran. |
| bl_nearbyA | List places of one kind (pharmacy, restaurant, gas station...) around a point, with address, phone and rating. Results are in Balad's own order (as on balad.ir, filters included), each with its straight-line distance
from the point. Text that names a category (پیتزا -> fast-food-restaurant) lists that whole category, as the
site does; |
| bl_placeA | Get one place's full details from Balad: address, phones, hours, open now, rating, amenities, photos, reviews.
|
| bl_reviewsA | Get one page of user reviews of a place on Balad, newest first, with stars and the rating breakdown.
|
| bl_reverse_geocodeA | Turn coordinates into a Persian street address with city, county and neighbourhood (reverse geocoding). Use it when the user gives a point or a map pin and wants to know where it is. For the opposite (address or name -> coordinates) use bl_search. Covers Iran only; elsewhere it answers with an error. |
| bl_routeA | Get driving routes in Iran with distance, travel time in current traffic, tolls, roads and traffic-zone warnings. Returns up to 3 routes, suggested first, like balad.ir's directions page; |
| bl_nearest_by_driveA | Rank places of one kind around a point by driving time from it in current traffic, quickest first. Use it for "which pharmacy / gas station / hospital can I reach fastest from here". It takes Balad's top
|
| bl_along_routeA | Find places of one kind (gas station, restaurant, pharmacy...) along the suggested driving route between two points. Use it for "a gas station on my way to Shiraz" or "a cafe on the way home". Places are ordered by where they
come on the route ( |
| bl_categoriesA | List Balad's place categories with the slug bl_nearby takes, grouped (food, health, shopping, services...). Call it when you need the exact slug for bl_nearby, bl_nearest_by_drive or bl_along_route (e.g. pharmacy, hospital, gas-station, atm, parking). |
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 9 tools
Each tool targets a clearly distinct operation: name search, category search around a point, place details, reviews, reverse geocoding, routing, drive-time ranking, along-route search, and category lookup. The potentially overlapping nearby/nearest_by_drive/along_route trio is explicitly differentiated in the descriptions and cross-referenced.
All tools use the bl_ prefix with snake_case and a consistent verb/noun or noun structure (bl_search, bl_reverse_geocode, bl_nearest_by_drive, bl_categories). No mixed conventions or ambiguous abbreviations.
Nine tools is well-scoped for a map/places server, covering search, details, reviews, routing, and category discovery without redundancy. Each tool earns its place and there is no filler.
The surface covers the core read-only map workflows: geocoding, reverse geocoding, place lookup, reviews, categories, and several routing variants. Minor gaps exist (e.g., no transit/walking routes, no write/review actions), but agents can work around these given the domain.