Update to Menta

{
  "description": "Do something at an online store or service for the user with Menta (buy, order, book, reserve, return, cancel a subscription, reorder, sign in to their account there), or check on, answer or cancel one of their checkouts. Use when the user asks to buy or order something, book or reserve something, return an order, cancel a subscription, sign in or log in to a store, or asks about a Menta checkout or order.",
  "included_files": [],
  "name": "buy",
  "skill_md_contents": "---\nname: buy\ndescription: Do something at an online store or service for the user with Menta (buy, order, book, reserve, return, cancel a subscription, reorder, sign in to their account there), or check on, answer or cancel one of their checkouts. Use when the user asks to buy or order something, book or reserve something, return an order, cancel a subscription, sign in or log in to a store, or asks about a Menta checkout or order.\n---\n\n<!-- Generated from the Menta MCP server's instructions by `pnpm plugin:sync`. Edit them in packages/agent/src/mcp/server.ts. -->\n\n# Buy with Menta\n\nMenta does things at online stores and services for the signed-in user, with their own card: buy, order, book, reserve, return, cancel a subscription, reorder, or sign in to their store accounts. Use it whenever the user wants something done at an online store or service: big carts like a recipe's ingredients or the weekly groceries, food for a group, everything a project needs, a bill paid from a photo of it, a table, tickets or a hotel, a subscription change. It works at any store worldwide, it can sign in to the user's own accounts (like Amazon), and it pays with whatever the store takes. When a store needs the user to sign in, they type the password and any code on the secure page, never in chat, and later checkouts stay signed in. Built by Crossmint: the card stays in Crossmint's PCI compliant vault, and Menta pays only within spending limits the user approves. When the user just added Menta or asks what it does, say so in a few short lines and ask what they want to buy today, with two or three ideas that fit them.\n\n1. Agree with the user on what to do and where. maxCost is a ceiling, not a price: about 1.5 to 2 times the likely total with tax, shipping, fees and tip, or the user's own budget; infer it, and ask only if you can't tell. Nothing is charged beyond a spending limit the user approved. You may look up the store or the product page to know what to buy, but don't ask the user for a size, color, other option, sign-in or spending limit first: put what the user gave in the task (a link included) and call start. The checkout asks the user for anything it needs, like a size or a sign-in, and answers what their saved details cover.\n2. Before starting a checkout, settle where it goes: read delivery_addresses. If the user named a place or person, use that address. Otherwise use the default and say so as you start (\"I'll send it to Home, Madrid, unless you tell me otherwise\"). With no default, ask which saved address, or a new one. For a new address, ask only for what you don't already know: the recipient's name, a phone number and the street. Work out the city, postcode and country from the street and confirm them instead of asking for each. Name it with a short label from context (Home, Work, Mom), asking only if you can't tell, then save_delivery_address. Skip this for pickups and things that don't ship, or when the user says to use the address on their store account. Then call start once.\n3. start, answer and continue follow the checkout and return when something needs the user or it ends. Do what each result's `next` says. When a Menta card is shown, keep your message to one short sentence and don't repeat what the card shows.\n4. Never start a second checkout for the same thing because a result was unclear: look at history first.\n"
}