Skip to main content
Glama

Nova Poshta: find a branch or parcel locker

np_find_branch
Read-only

Find Nova Poshta branches or parcel lockers by city, branch number, or street; get address, opening hours, weight limit, and current working status.

Instructions

Nova Poshta branches (відділення) and parcel lockers (поштомати) in a city or village: address, opening hours, weight limit and whether it is working now. Narrow it with a branch number or part of a street name.

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": {
      "city": "<city>"
    },
    "name": "np_find_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity or village name, Ukrainian spelling works best
kindNoOnly branches or only parcel lockers
limitNoHow many to return, 5 by default
queryNoBranch number or part of the street, e.g. "12" or "Хрещатик"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value beyond that by disclosing the returned fields — address, opening hours, weight limit, and live working status — which is the main behavioral unknown for a lookup with no output schema. It does not mention result ordering or what happens when a city has no matches.

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, front-loaded with the resource and the returned data, then the refinement hint. No filler and no repetition of the tool name.

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 four-parameter read-only lookup with no output schema, the description covers resource, scope, return fields, and result narrowing. Only minor items are absent, such as default result volume and behavior on empty results, which the schema's limit default partly mitigates.

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 city, kind, limit and query are already fully documented with examples. The description restates the narrowing idea for the query parameter but adds no syntax or behavior beyond the schema, so the baseline of 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?

"Nova Poshta branches (відділення) and parcel lockers (поштомати) in a city or village" states a specific resource and scope, and the sentence goes on to enumerate what comes back (address, hours, weight limit, working status). No sibling (np_quote, np_track, mono_rates) overlaps with this lookup, so an agent can route to it unambiguously.

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

Usage Guidelines3/5

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

"Narrow it with a branch number or part of a street name" is the only usage steering and it addresses refinement rather than tool selection. There is no statement of when not to use it or when a sibling is preferable, though the siblings are unrelated enough that this gap is small.

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