Location & Demand Intelligence

İBB Traffic Operating Window Planner

traffic-index-operating-window-planner

Convert official hourly traffic history into explainable low-congestion operating windows. Unofficial, independent Actor; not affiliated with or endorsed by any named source publisher. — $0.02/call, x402 (USDC on base).

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": {
      "requestId": "<requestId>",
      "windows": "<windows>",
      "maxTotalChargeUsd": "<maxTotalChargeUsd>"
    },
    "name": "traffic-index-operating-window-planner"
  }
}

Input Schema

Name	Required	Description
`windows`	Yes	One paid decision at most per new, non-duplicate window plan.
`requestId`	Yes	Reuse only for the exact same input. A changed payload with the same key fails closed.
`maxTotalChargeUsd`	Yes	Checked before any decision claim and again by the Apify platform.

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 17, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The description discloses pricing ('$0.02/call'), payment method ('USDC on base'), and independence ('Unofficial, independent Actor'), which go beyond the annotations. It does not contradict annotations and adds context not available from structured fields.

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?

The description is extremely concise (two sentences) with the core purpose front-loaded, followed by essential disclaimers and pricing. Every sentence earns its place with no redundancy.

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

Completeness3/5

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

The tool has moderate complexity and no output schema, yet the description does not explain the return format or how the operating windows are computed beyond stating the conversion. It remains adequate for selection but not fully sufficient for invocation without relying on the schema's input descriptions.

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 coverage is 100% with detailed parameter descriptions, so the baseline is 3. The main description adds no extra parameter semantics beyond the high-level 'traffic history into windows' concept, but schema already handles the burden.

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?

The description states a specific verb ('Convert') and resource ('official hourly traffic history') with a clear output ('explainable low-congestion operating windows'). This clearly distinguishes it from sibling tools focused on earthquakes, parking, and real estate.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance is provided. The description only states what the tool does, leaving usage to be inferred from the domain and tool name.

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

All Location & Demand Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?