Skip to main content
Glama

salik_toll_estimate

Read-onlyIdempotent

Calculate the VAT-inclusive Salik toll in AED for a chosen day and time using Dubai's official variable-pricing windows.

Instructions

Deterministic Salik toll (AED) for a time of day using the official variable-pricing windows. Figures are VAT-inclusive (5% VAT applies at the point of use from 2026-06-01).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "salik_toll_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNo'weekday' or 'sunday' (Sunday has a flat toll outside the free window).weekday
time_of_dayNo24-hour HH:MM, e.g. '08:00'.08:00

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world safety. The description adds genuinely new context: results are deterministic (no rate fluctuation or randomness), figures are VAT-inclusive, and the 5% VAT rule takes effect from 2026-06-01 — a time-dependent behavior an agent could not get from the schema. It stops short of stating what happens in the free window or which timezone applies.

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?

Two sentences, front-loaded with the core output and currency, followed by the VAT qualifier. No wasted text; the parenthetical VAT note is dense but earns its place. Slight loss for the line-wrapped formatting that makes the qualifier feel like an afterthought.

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?

An output schema exists, so return-value explanation is unnecessary, and the tool is a cheap read with only two optional parameters. The remaining gap is minor but real: no statement about timezone assumptions or behavior inside the free window, which matters for a toll estimator.

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?

Schema description coverage is 100%, so both parameters (day, time_of_day) are already documented with defaults and allowed values. The description reinforces the temporal framing but adds no syntax or edge-case detail beyond the schema. Baseline 3 applies.

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

Purpose4/5

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

States a specific verb+resource: returns a deterministic Salik toll in AED for a given time of day, computed from the official variable-pricing windows. That is concrete and actionable. It does not, however, contrast itself with the sibling rta_salik_tariff, so the agent must infer which of the two to call.

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

Usage Guidelines3/5

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

Usage is only implied: it is the tool to call when a specific toll amount for a specific time is needed. There is no explicit 'use this instead of rta_salik_tariff when...' routing, no mention of prerequisites, and no statement of what the tool does not cover (e.g. multiple gates, monthly passes).

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