Skip to main content
Glama

Estimate RoutersUA dispatch and delivery

routersua_estimate_delivery
Read-onlyIdempotent

Estimate whether a RoutersUA order placed now ships today and by which date Nova Poshta usually delivers it, from the current time in Kyiv and the store's same-day cut-off: 17:30 Monday to Friday, 16:30 on Saturday, Sunday and public holidays. Use it when the user asks when an order would ship or arrive; for delivery points use routersua_find_delivery_points, and for delivery cost and payment methods routersua_get_store_policy. Transit usually takes 0 to 2 days after shipping; dates are YYYY-MM-DD. Public holidays are not known to it; products on backorder ship from their backorder_ship_date instead.

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": "routersua_estimate_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
now_kyivYes
ship_dateYes
delivery_byYes
ships_todayYes
today_cutoffYes
delivery_fromYes
delivery_termsYes
ship_date_cutoffYes
delivery_terms_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description layers on genuinely new behavior: the Kyiv-time basis, the exact cut-off schedule including weekend/holiday differences, a 0-2 day transit window, an explicit limitation ('Public holidays are not known to it'), and backorder override rules.

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?

Purpose and cut-off facts are front-loaded, and nearly every clause carries operational detail (cut-offs, transit, format, holiday caveat, backorder). It is a dense single block, however, and the cut-off schedule could be separated from the behavioral caveats for faster scanning.

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?

The tool takes no inputs and has an output schema, so return values need no explanation; the description nonetheless supplies the cut-off rules, transit range, date format and edge cases an agent needs to answer correctly.

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?

There are zero parameters, so the baseline is 4; the description usefully clarifies that the estimate is anchored to 'placed now' rather than a caller-supplied timestamp, which explains why no input exists.

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 and resource ('Estimate whether a RoutersUA order placed now ships today and by which date Nova Poshta usually delivers it') and immediately separates itself from sibling tools by naming routersua_find_delivery_points and routersua_get_store_policy with their own purposes.

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?

It gives both the trigger ('Use it when the user asks when an order would ship or arrive') and the routing rules away from it: delivery points go to routersua_find_delivery_points, cost and payment methods go to routersua_get_store_policy. Nothing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources