Skip to main content
Glama

Find Nova Poshta delivery points

routersua_find_delivery_points
Read-onlyIdempotent

Find Nova Poshta branches and parcel lockers in a Ukrainian city where a RoutersUA order can be collected, from the directory the store checkout uses. Use it when the user asks where to collect an order or which point is near them; for ship and delivery dates use routersua_estimate_delivery, and for delivery cost and payment routersua_get_store_policy. If the city name matches several places, the result lists them; call again with city_ref. At most 30 points come back; more_points true means there are more, so narrow with query. An unknown city returns an error.

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_find_delivery_points"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity or village name in Ukrainian or Russian, e.g. "Київ", "Одеса", "Львів". Give city or city_ref.
typeNobranch for Nova Poshta branches and partner points, locker for parcel lockers, all for both.all
queryNoA branch or locker number (73) or part of the address (a street name) to narrow the list.
city_refNoThe ref of a city from the cities list of an earlier result, to pick one of several matches.

Output Schema

NameRequiredDescriptionDefault
cityNo
citiesNo
pointsNo
more_pointsNo
delivery_termsYes
delivery_terms_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: ambiguity handling (several city matches are listed, re-call with city_ref), a hard result cap of 30 with a more_points flag, and an error on unknown city. These are operational traits an agent cannot get from the annotations or schema.

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?

Four sentences, each earning its place: purpose, triggers plus alternatives, ambiguity and pagination behavior, error case. Front-loaded with the primary use case and free of filler.

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 an output schema present, the description needn't explain return values, and it still covers the failure mode, the result cap, and the disambiguation loop. For a 4-parameter, read-only lookup tool this is complete enough to call correctly on the first try.

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 the baseline is 3, but the description adds the workflow meaning behind city_ref (its purpose is the second call after a multi-match) and behind query (narrowing when more_points is true), which the schema only states statically. It does not add format or syntax detail beyond that.

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 (find), specific resource (Nova Poshta branches and parcel lockers), geographic scope (a Ukrainian city), and the collection-use context (where a RoutersUA order can be collected). An agent can immediately tell it apart from estimate_delivery and get_store_policy.

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?

Gives an explicit trigger ('when the user asks where to collect an order or which point is near them') and names two alternatives with the conditions that select them (dates → estimate_delivery, cost/payment → get_store_policy). Nothing is left to inference about routing.

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