Skip to main content
Glama
Sign In
neshan-mcp

neshan-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Tehran traffic and odd-even zone check

ns_zone_check
Read-onlyIdempotent

Check whether a point lies inside Tehran’s traffic or odd-even air-pollution zone and return active plan hours before you drive.

Instructions

Check whether a point is inside Tehran's traffic-plan zone or odd-even (air-pollution) zone, with plan hours.

Use before driving to central Tehran: the traffic zone needs a permit while the plan runs, the odd-even zone restricts plates on alternate days. plans gives active hours. To avoid them use ns_route avoid_*.

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": {
      "location": "<location>"
    },
    "name": "ns_zone_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYesPoint 'lat,lng'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuine domain context beyond that: the permit requirement during traffic-plan hours, the alternate-day plate rule, and the fact that `plans` carries active hours. No mention of rate limits or coverage boundaries, but little is needed for a read-only point lookup.

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

Conciseness5/5

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

Two tight paragraphs with the capability stated first and the usage/alternative guidance second. Every clause carries information — zone definitions, permit rule, output field, and the routing alternative — with no filler.

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

Completeness4/5

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

With one required parameter, no output schema, and rich annotations, the description covers what the tool decides and what `plans` supplies. A little more detail on the shape of `plans` (e.g., weekday/hours granularity) would fully close the gap, but an agent can call this correctly as written.

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

Parameters3/5

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

The single parameter has full schema coverage, with the schema itself documenting the 'lat,lng' point format. The description adds no syntax, coordinate-order, or boundary details for `location`, so it does not exceed the baseline that a fully documented schema already establishes.

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?

States a specific verb and resource: checking whether a point falls inside Tehran's traffic-plan zone or odd-even (air-pollution) zone, and notes it returns plan hours. The two zone types are named and differentiated, so an agent knows exactly what question this tool answers.

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

Usage Guidelines4/5

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

Explicitly frames the use case ('Use before driving to central Tehran') and explains what each zone means in practice (permit required vs. plate restriction on alternate days). It also routes the agent to ns_route avoid_* when the goal is avoidance rather than checking, though it gives no guidance on when a sibling like ns_air_quality or ns_nearby would be the better call.

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