Skip to main content
Glama

Order a free postal pack (Bosca) for the user

request_postal_pack

Orders a free insured postal pack for a person at a Republic of Ireland address and returns the Bosca number. This is the real order: the request is created when you call it, and for gold lots of any value the pack is posted to the address given with no further step from the person. Silver, mixed lots and bullion are registered and arranged on WhatsApp instead; the response says which happened. The person gets a receipt email with a single-use cancel link. Before calling: have the person's name, full address with Eircode, email, phone, what they are sending (gold, silver or mixed) with a rough description and rough value, their agreement to be contacted, and their agreement to the terms statement in accepts_terms. Explain the process first (get_postal_pack_info): items weighed and XRF tested on camera, an itemised offer at the live published rate on the day of testing (no payout is promised), the parcel travels at Liffey Metals' risk whatever the value, paid by bank transfer the same day they accept, one photo ID checked before payment. Lots worth more than 1,000 euro can be brought to us in person in Dublin, by appointment, and tested while you watch; message us on WhatsApp to arrange a time. Smaller lots go by post. Do not collect or pass ID documents. Errors name the field to fix.

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": {
      "name": "<name>",
      "address_line1": "<address_line1>",
      "town": "<town>",
      "county": "<county>",
      "eircode": "<eircode>",
      "email": "<email>",
      "phone": "<phone>",
      "metal_type": "<metal_type>",
      "rough_description": "<rough_description>",
      "consent_contact": "<consent_contact>",
      "accepts_terms": "<accepts_terms>"
    },
    "name": "request_postal_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe person's full name, as it should appear on the pack
townYesTown or city
agentNoOptional: the name of the assistant or model making the request, recorded with the lead
emailYesThe person's own email: the receipt, the offer and every update go there
phoneYesPhone number, a mobile preferred, e.g. 087 123 4567 or +353 87 123 4567
countyYesCounty in the Republic of Ireland, e.g. Cork, Mayo, Dublin (Northern Ireland addresses are refused with the alternative)
eircodeYesThe person's Eircode, 7 characters, e.g. D02 X285 (finder.eircode.ie)
item_countNoOptional rough number of items
metal_typeYesWhat they are sending: gold, silver or mixed
accepts_termsYesMust be true, and only after the person has agreed to this statement, which you read to them: "I am 18 or over and I own the items I will send, or am authorised to sell them. I accept the Liffey Metals Postal Selling Terms and Seller Agreement (liffeymetals.com/terms/postal and liffeymetals.com/legal/seller-agreement). I understand that if I decline the offer my items are returned free, and that a postage deduction applies only as those terms describe."
address_line1YesHouse or apartment and street, or townland
address_line2NoOptional second address line
consent_contactYesMust be true: the person agrees to be emailed about the pack and contacted about their items
source_of_itemsNoOptional: where the items came from, if the person said; defaults to other
rough_descriptionYesA rough description of the items, e.g. 'two 9ct rings and a broken 18ct chain, about 12 g'
estimated_value_eurNoRough total value in euro; ask for it. It sets the value band on the request and the route: gold of any value goes straight to a pack, and under 300 euro there is no pack. Left out, the lot is recorded in the 300 to 500 euro band.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / estimated_value_eur / description
      Previous value: -"Rough total value in euro; ask for it. It sets the value band on the request and the route: gold up to 2,000 euro goes straight to a pack, lots over 2,000 euro are arranged on WhatsApp, and under 300 euro there is no pack. Left out, the lot is recorded in the 300 to 500 euro band."New value: +"Rough total value in euro; ask for it. It sets the value band on the request and the route: gold of any value goes straight to a pack, and under 300 euro there is no pack. Left out, the lot is recorded in the 300 to 500 euro band."
  2. Changed6 schema fields changed
    • addedInput schema / properties / accepts_terms
      Added value: +{
      +  "const": true,
      +  "description": "Must be true, and only after the person has agreed to this statement, which you read to them: \"I am 18 or over and I own the items I will send, or am authorised to sell them. I accept the Liffey Metals Postal Selling Terms and Seller Agreement (liffeymetals.com/terms/postal and liffeymetals.com/legal/seller-agreement). I understand that if I decline the offer my items are returned free, and that a postage deduction applies only as those terms describe.\"",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / consent_contact / description
      Previous value: -"Must be true: the person agrees to be emailed the confirmation link and contacted about the pack"New value: +"Must be true: the person agrees to be emailed about the pack and contacted about their items"
    • changedInput schema / properties / email / description
      Previous value: -"The person's own email: the confirmation link goes there and nothing ships until they click it"New value: +"The person's own email: the receipt, the offer and every update go there"
    • changedInput schema / properties / estimated_value_eur / description
      Previous value: -"Optional rough total value in euro, if the person gave one; it preselects the value band they confirm"New value: +"Rough total value in euro; ask for it. It sets the value band on the request and the route: gold up to 2,000 euro goes straight to a pack, lots over 2,000 euro are arranged on WhatsApp, and under 300 euro there is no pack. Left out, the lot is recorded in the 300 to 500 euro band."
    • addedInput schema / properties / source_of_items
      Added value: +{
      +  "description": "Optional: where the items came from, if the person said; defaults to other",
      +  "enum": [
      +    "inherited",
      +    "own purchase",
      +    "gift",
      +    "business stock",
      +    "other"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "address_line1",
      -  "town",
      -  "county",
      -  "eircode",
      -  "email",
      -  "phone",
      -  "metal_type",
      -  "rough_description",
      -  "consent_contact"
      -]New value: +[
      +  "name",
      +  "address_line1",
      +  "town",
      +  "county",
      +  "eircode",
      +  "email",
      +  "phone",
      +  "metal_type",
      +  "rough_description",
      +  "consent_contact",
      +  "accepts_terms"
      +]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only mark it non-read-only, non-destructive and non-idempotent; the description adds that the order is created immediately on call, that a receipt email with a single-use cancel link goes to the person, that the response reveals which fulfilment route was taken, and that errors name the field to fix. It also sets a boundary not derivable from annotations: do not collect or pass ID documents, and no payout is promised.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and reasonably organised, but bloated by a full narrative of the testing/offer/payment process that arguably belongs to get_postal_pack_info and how_selling_works. The trip-planning paragraph about in-person Dublin appointments is useful but sits awkwardly inside an ordering tool.

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 16-parameter, 11-required mutation with no output schema, the description covers prerequisites, side effects and route outcomes well. It does not say what happens if the caller submits twice for the same person, which matters given idempotentHint=false.

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; the description goes beyond it by tying estimated_value_eur to route selection (no pack under 300 euro, omitted values land in the 300-500 band) and by requiring the accepts_terms statement be read and agreed before the call. It mostly reinforces what the schema already documents, so it is not a strong addition, but the value-band routing effect is worth restating.

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 and resource (orders a free insured postal pack for an ROI address) and names a concrete return value (the Bosca number). It explicitly contrasts itself with the informational sibling get_postal_pack_info and with the WhatsApp/in-person routes, so an agent can place it precisely.

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

Usage Guidelines5/5

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

Gives explicit when-to-use routing: gold of any value is posted with no further step, while silver, mixed and bullion are registered via WhatsApp instead, and lots over 1,000 euro can go to Dublin by appointment. It also states prerequisites (collect name, address with Eircode, email, phone, metal type, description, value, consent) and instructs calling get_postal_pack_info first.

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