Skip to main content
Glama

Przygotuj zamówienie (link, klient płaci sam)

zloz_zamowienie

Sklada KOMPLETNE zamowienie (pozycje + e-mail + adres dostawy + opcjonalnie dostawa/paczkomat) i zwraca ZASZYFROWANY, podpisany link jednego kliknieca do /zamowienie-agenta. To narzedzie NIE tworzy koszyka ani zamowienia w sklepie i NIGDY nie placi — klient klika link, widzi zywe ceny i adres, i placi SAM w naszej kasie. Suma zamowienia powyzej 500 zl nie jest obslugiwana: narzedzie zwraca blad z linkiem do zwyklego koszyka. Bez pola "dostawa" narzedzie zwraca liste zywych opcji dostawy, a link powstaje z najtansza opcja. Maks. 10 pozycji.

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": {
      "pozycje": "<pozycje>",
      "email": "<email>",
      "adres": "<adres>"
    },
    "name": "zloz_zamowienie"
  }
}

Input Schema

NameRequiredDescriptionDefault
adresYes
emailYesE-mail klienta.
dostawaNoID opcji dostawy (opcjonalne).
pozycjeYes
paczkomatNoKod punktu InPost od klienta, np. WAW123M (opcjonalne).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say it is a non-destructive, non-open-world write; the description adds substantial context beyond that: no cart or shop order is created, no payment ever occurs, the returned link is encrypted and signed, the 500 zl ceiling produces a specific error payload, and the missing-dostawa case returns a live delivery-option list. It also discloses the 10-item cap and the substitution rule (cheapest option chosen) — behavior an agent could not infer from the annotations.

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?

The most important facts — what is produced and what is explicitly NOT done — are front-loaded, and each sentence carries a distinct constraint. The trailing "Maks. 10 pozycji" merely repeats the schema's maxItems/maximum, a minor redundancy.

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?

For a mutation-flavored tool with a nested object schema and no output schema, the description covers the success artifact (signed link), the over-limit failure path, and the no-delivery fallback return value, so an agent knows what comes back in every branch. Nothing needed to invoke it correctly appears to be missing.

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?

With 60% schema coverage, the description carries real weight: it explains the semantics of the optional "dostawa" parameter (its absence changes the return value and defaults the link to the cheapest option), confirms paczkomat belongs to the order payload, and reiterates the 10-item limit on pozycje. The nested address fields are left to the schema, which documents them adequately.

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 action (composing a complete order from items, e-mail, address and optional delivery), states the exact artifact returned (an encrypted, signed one-click link to /zamowienie-agenta), and explicitly negates what siblings like zloz_koszyk/compose_cart do ("NIE tworzy koszyka ani zamowienia w sklepie"). An agent can distinguish this from the cart- and order-placing siblings 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?

Clear conditions are given: the customer pays themselves via the link, totals above 500 zl are not supported and yield an error with a plain-cart link, and omitting "dostawa" switches the tool into a delivery-options-returning mode using the cheapest option. It stops short of naming sibling tools for the fallback path (it only says "zwykly koszyk"), so the routing is implied rather than explicit.

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