Skip to main content
Glama

Nova Poshta: delivery cost and date

np_quote
Read-only

Calculate Nova Poshta parcel delivery cost and estimated arrival time between two cities by name, using weight, declared value, and service type.

Instructions

What a Nova Poshta parcel between two places costs and when it would arrive if sent now. Takes city names, not codes. Use it for "how much to send" and "how long does delivery take" questions about Nova Poshta.

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": {
      "from": "<from>",
      "to": "<to>",
      "weight_kg": "<weight_kg>"
    },
    "name": "np_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesCity the parcel goes to
fromYesCity the parcel leaves from
serviceNoBranch to branch by default; Doors means courier pickup or delivery
weight_kgYesWeight in kilograms
declared_value_uahNoDeclared value in hryvnias, 300 by default

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the description only needs to add context. It does add two useful traits: the input format constraint (city names, not codes) and the temporal framing ("if sent now"), which signals the quote is time-dependent and non-binding. It does not say what the returned figure represents beyond cost/date, nor whether the estimate is guaranteed.

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?

Three short sentences, front-loaded with what the tool returns and followed by the input constraint and usage triggers. The quoted example questions are slightly redundant with the opening sentence but still earn their place as routing cues.

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?

For a read-only quote tool with five fully documented parameters and no output schema, the definition covers purpose, input format, and triggering questions. It could go one step further and state the currency of the returned cost and whether the arrival estimate is a date or a range, but nothing essential to invoking it correctly is missing.

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 all five parameters, including the service enum and the declared-value default of 300 UAH, are already documented in the schema. The description only reinforces the from/to semantics with "Takes city names, not codes" and says nothing about weight, service mode, or declared value, so baseline 3 applies.

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 names a specific verb-like outcome (cost and arrival date) and a specific resource (a Nova Poshta parcel between two places), so the agent knows exactly what it computes. It is clearly separable from np_track (tracking an existing parcel), np_find_branch (locations) and mono_rates (currency), because the first sentence is about pricing and delivery time for a prospective shipment.

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?

It gives explicit trigger questions: "how much to send" and "how long does delivery take" for Nova Poshta. There are no when-not conditions and no named alternatives, but the framing as a pre-send estimate is clear enough that misuse is unlikely.

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