Skip to main content
Glama
Sign In
neshan-mcp

neshan-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Neshan directions

ns_route
Read-onlyIdempotent

Get car, motorcycle, bicycle or walking directions with distance, travel time and turn-by-turn steps. Plan depart or arrival times, add up to three stops, and avoid tolls or traffic zones.

Instructions

Get car, motorcycle, bicycle or walking directions on Neshan: distance, travel time and turn-by-turn steps.

Points are 'lat,lng' (geocode with ns_search). Car trips return 2-3 routes, the first being Neshan's pick: distance_km, duration_min (live, or for depart_at), via and flags toll_road, enters_traffic_zone, enters_odd_even_zone when true. depart_at / arrive_by (car; Tehran, Karaj, Mashhad forecast) cannot combine with stops or avoid_*. Steps (first route, up to 40): do Persian text, m metres, s seconds. zones lists traffic plans with hours. Many destinations: ns_travel_times; bus/metro: ns_transit_route.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "origin": "<origin>",
      "destination": "<destination>"
    },
    "name": "ns_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoTravel mode.car
stepsNoTurn-by-turn steps for the first route.
stopsNoWaypoints in order, each 'lat,lng' (max 3).
originYesStart 'lat,lng', e.g. '35.6997,51.3380'.
arrive_byNoCar only: Tehran time 'YYYY-MM-DD HH:MM' (Gregorian) to arrive by. Gives leave_by.
depart_atNoCar only: Tehran time 'YYYY-MM-DD HH:MM' (Gregorian) to leave at, e.g. '2026-11-01 08:00'. Gives arrive_at.
avoid_tollsNoCar only: avoid toll roads.
destinationYesEnd 'lat,lng'.
avoid_odd_evenNoCar only: avoid the odd-even zone.
avoid_traffic_zoneNoCar only: avoid Tehran's traffic-plan zone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/openWorld, and the description still adds substantive behavior: car trips return 2-3 routes with the first as Neshan's pick, route-level flags (toll_road, traffic zone, odd-even) appear only when true, forecast data is limited to Tehran/Karaj/Mashhad, and steps are capped at 40 for the first route only. That is real disclosure rather than restating safety hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core capability, then organized into return shape, constraints, and sibling routing — no filler sentences. It is telegraphic to the point of terseness (backticked field names, 'flags toll_road' fragments), which is dense but occasionally reads like notes rather than prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 10 parameters and no output schema, the description compensates by enumerating the return fields (distance_km, duration_min, via, flags, zones, steps) and the constraints governing them. An agent can invoke it correctly and anticipate the response without further documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3; the description earns more by adding cross-parameter constraints absent from the schema — depart_at/arrive_by being car-only, forecast-city limited, and mutually exclusive with stops and avoid_*. It also clarifies the 'lat,lng' point format and that steps apply to the first route only, though per-flag semantics (avoid_odd_even vs avoid_traffic_zone) are left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource — 'Get car, motorcycle, bicycle or walking directions on Neshan' — and immediately names the returned payload (distance, travel time, turn-by-turn steps). It also explicitly separates itself from ns_travel_times (many destinations) and ns_transit_route (bus/metro), so an agent can pick it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names alternatives with the conditions that select them: 'geocode with ns_search', 'Many destinations: ns_travel_times', 'bus/metro: ns_transit_route'. It also gives a hard usage constraint — depart_at/arrive_by cannot be combined with stops or avoid_* — which is when-not guidance rather than just context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools