Skip to main content
Glama

Nova Poshta: where is the parcel

np_track
Read-only

Track up to 20 Nova Poshta parcels by ТТН to check location, expected delivery, and pickup status; add sender or recipient phone to retrieve weight, cost, and contents.

Instructions

Current status of Nova Poshta parcels by tracking number (ТТН, 14 digits, usually starting with 2 or 5): where the parcel is, when it is expected, whether it was picked up. Up to 20 numbers at once. Give the sender or recipient phone to also get weight, cost and contents.

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": {
      "numbers": "<numbers>"
    },
    "name": "np_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneNoSender or recipient phone as 380XXXXXXXXX, unlocks the full details
numbersYesTracking numbers (ТТН)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint) and reach (openWorldHint), so the description correctly spends its words elsewhere: the 20-number batch cap and the fact that supplying a phone broadens the payload to weight, cost and contents. That batch limit and the enrichment behavior are not visible in the annotations and materially shape how an agent should call it.

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 sentences, no filler: the first front-loads the core capability and the returned fields, the second carries the batch limit and the optional enrichment. Every clause conveys a fact an agent would otherwise have to guess.

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?

There is no output schema, so the description carries the burden of describing results, and it does so at a useful level (status, ETA, pickup state, plus optional weight/cost/contents). For a two-parameter read-only lookup this is essentially complete; only exact response shape or error behavior for invalid TTNs is left implicit.

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 real meaning: it explains the TTN concept and gives a typical shape, and it concretizes what the phone parameter unlocks (weight, cost, contents) beyond the schema's vague 'unlocks the full details'. Minor deduction because '14 digits' loosely conflicts with the schema's 11-18 digit pattern, which could mislead an agent about validation.

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+resource: retrieve current status of Nova Poshta parcels by tracking number. It further enumerates the three facts returned (location, expected date, pickup state), so an agent knows exactly what question this answers and can distinguish it from np_find_branch (branch lookup) and np_quote (pricing) without opening any schema.

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?

Usage context is clear: this is the tool for tracking existing parcels given TTN numbers, and the description explains the optional-phone path as an upgrade rather than a requirement. It gives no explicit 'do not use for X' or named alternative, which keeps it just short of a 5.

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