Skip to main content
Glama
Sign In
@placraftic/mcp-server

@placraftic/mcp-server

by placraftic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_nova_poshta_waybill

Create a Nova Poshta electronic waybill (TTN) for an order using your studio sender settings. Provide order ID and optional package details to generate shipping documents.

Instructions

Generate a Nova Poshta electronic waybill (TTN) for an order using studio sender settings

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": {
      "orderId": "<orderId>"
    },
    "name": "create_nova_poshta_waybill"
  }
}

Input Schema

NameRequiredDescriptionDefault
weightNoEstimated package weight in kilograms (e.g. '0.5', default: '0.5')
orderIdYesUnique numeric ID of the order to ship
descriptionNoParcel description for Nova Poshta invoice (default: '3D Printed Parts')
seatsAmountNoNumber of box seats (default: '1')
serviceTypeNoDelivery type: 'WarehouseWarehouse' (branch) or 'WarehouseDoors' (courier)
declaredValueNoDeclared package value in UAH (e.g. '250', default: order total)
recipientPhoneNoOverride recipient phone number in international format (+380...)
recipientCityRefNoNova Poshta Ref for recipient city
recipientLastNameNoOverride recipient last name
recipientFirstNameNoOverride recipient first name
recipientWarehouseRefNoNova Poshta Ref for recipient branch/warehouse

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It hints that sender data comes from stored studio settings and recipient fields can be overridden, but it omits whether this is a write operation with real-world cost, whether it is idempotent, what happens on failure, and what permissions are required.

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?

A single front-loaded sentence with no filler; the verb, resource, and scoping context are all in the opening clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations, no output schema, and 11 parameters, the description is thin. It never indicates what the call returns (TTN number/ref), how errors surface, or the side effects of creating a live shipping document, leaving the agent under-informed before invoking it.

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% and every parameter including defaults is documented in the schema itself, so the baseline is 3. The description adds only the indirect point that unspecified values fall back to studio settings and order data, not new semantics for any individual parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Generate) and resource (Nova Poshta electronic waybill, TTN) scoped to an order, which is clear and concrete. However, it does not differentiate itself from the sibling print_waybill or track_shipment, so an agent must infer which of the waybill-related tools to call.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of prerequisites (e.g., whether the order must already exist or have a delivery address). The sibling print_waybill is left unaddressed, so routing between the two is guesswork.

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