Skip to main content
Glama

Edit shop account settings

account_edit

Modify the settings of the authenticated shop account. All fields are optional. Covers: basic info (name, address, legal numbers), receipt display options, order requirements, feature flags (stock, barcodes, variations, webshop, coupons...), delivery method toggles, and third-party integrations (PayPal, Prestashop, Yavin, Viva.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoGPS latitude
lngNoGPS longitude
cityNoCity
phoneNoContact phone number
countryNoCountry
currencyNoCurrency code (e.g. EUR, USD)
languageNoLanguage code (e.g. fr, en)
postCodeNoPostal/ZIP code
shopNameNoStore name
deliv_barNoEnable counter/bar sales
pdffooterNoFooter text for PDF invoices
urlwebsiteNoURL of the shop website
webShopURLNoWebshop URL
adressline1NoAddress line 1
enableYavinNoEnable Yavin payment terminal
webShopCol1NoWebshop background color 1 (hex)
webShopCol2NoWebshop background color 2 (hex)
webShopCol3NoWebshop background color 3 (hex)
webShopLangNoWebshop language
yavinSecretNoYavin secret code
yavinSerialNoYavin terminal serial number
defaultVatIDNoDefault VAT rate identifier
enable_stockNoActivate inventory/stock management
webShopColT1NoWebshop text color 1 (hex)
webShopColT2NoWebshop text color 2 (hex)
webShopColT3NoWebshop text color 3 (hex)
deliv_defaultNoDefault delivery method ID
deliv_deliverNoEnable home delivery management
paypalAddressNoPayPal email address for collecting payments
prestaShopURLNoPrestashop store URL
receiptFooterNoFooter text printed on receipts
receiptHeaderNoHeader text printed on receipts
vivaAccoundIDNoViva.com account ID
deliv_takeAwayNoEnable takeaway orders
enable_couponsNoEnable coupon management
enable_creditsNoEnable customer credit management
deliv_drivethruNoEnable drive-thru orders
deliv_tablePlanNoEnable table/seats management
enable_barcodesNoEnable barcode scanning
receipt_showVatNoDisplay VAT breakdown on tickets
enableVivaWalletNoEnable Viva.com payment collection
enable_delivShopNoActivate deliveries via Deliv.shop
isWebShopEnabledNoActivate the online webshop
prestaShopApiKeyNoPrestashop API key
enable_variationsNoEnable product variation management
enable_whiteLabelNoEnable white labeling (cannot be disabled once enabled)
deliv_relayDepositNoEnable delivery to a relay point
enable_departmentsNoActivate department/shelf management
orderRequires_dateNoDate selection required for each order
orderRequires_nameNoCustomer last name required for each order
receipt_showClientNoDisplay customer's name on tickets
receipt_showSellerNoDisplay seller's name on tickets
taxRegistrationNumNoVAT / tax registration number
vivaWalletMerchantNoViva.com Merchant ID
enable_relayDepositNoEnable pickup/relay point management
orderRequires_emailNoCustomer email required for each order
orderRequires_phoneNoCustomer phone required for each order
receipt_showAddressNoDisplay store's contact details on tickets
receipt_showCashboxNoDisplay cashier's name on receipts
receipt_showCommentNoShow order comment on tickets
receipt_showShopNameNoDisplay shop name on tickets
enable_weightForItemsNoEnable item weight management
orderRequires_addressNoCustomer address required for each order
orderRequires_commentNoComment required for each order
orderRequires_surnameNoCustomer first name required for each order
receipt_showGlobalVatNoDisplay global VAT total on tickets
whiteLabelAdminUserIDNoWhite label administrator user ID
companyRegistrationNumNoCompany registration number (RCS/SIRET)
receipt_showClientPhoneNoDisplay customer's phone number on tickets
defaultAccountingChapterNoDefault accounting chapter
enable_dateOfConsumptionNoEnable expiration date management
enable_departmentsGroupsNoEnable department group management
receipt_showClientAddressNoDisplay customer's address on tickets
receipt_showClientSurnameNoDisplay customer's first name on tickets
enable_descriptionsForItemsNoEnable descriptions for catalog items
orderRequires_deliveryChoiceNoDelivery method required for each order
pricesAreProvidedTaxIncludedNo0 = prices incl. VAT; 1 = prices excl. VAT
receipt_showPricesBeforeTaxesNoDisplay prices excl. VAT on tickets
enable_descriptionForVariationsNoEnable descriptions for variation choices
receipt_showCompanyRegistrationNumNoDisplay store's company number on receipts
orderRequires_CompanyRegistrationNumNoCustomer company number required for each order

TDQS

A3.7/5.0
Behavior2/5

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

Beyond the annotations (idempotentHint=false, destructiveHint=false), the description only states it modifies settings. It does not disclose consequences of changes, auth requirements (implied by 'authenticated'), rate limits, or side effects like immediate propagation. The minimal behavioral detail leaves the agent underinformed.

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?

The description is a single, front-loaded sentence stating the main action, followed by a succinct list of categories. Every sentence is necessary, and there is no extraneous text. It is appropriately sized for the tool's complexity.

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

Completeness3/5

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

For a tool with 81 parameters and no output schema, the description covers the main categories but omits important context: it does not specify that only provided fields are updated (implied by optional), the scope of effect (only authenticated shop), or error handling. It is adequate but lacks completeness for safe autonomous use.

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% with individual parameter descriptions. The tool description adds value by grouping the 81 parameters into categories (basic info, receipt display, feature flags, etc.), aiding comprehension. This organization goes beyond the schema and justifies a score above baseline 3.

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 clearly states the tool modifies settings of the authenticated shop account, aligning with the title. It distinguishes from sibling tools like account_create (create new account) and account_show_infos (view info), as it is explicitly for editing existing settings.

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?

The description indicates that all fields are optional, implying partial updates, but does not explicitly state when to use this tool versus alternatives (e.g., account_create for new accounts) or provide exclusions. No when-not guidance is given.

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.

TDQS

A3.7/5.0
Disambiguation5/5

Each tool targets a distinct entity or action (account, client, order, product, payment, VAT, etc.), with clear naming like 'account_create' vs 'account_edit' and 'data_list_' prefixed listings. No overlapping purposes detected.

Naming Consistency5/5

All tool names use snake_case and follow a consistent verb_noun pattern (e.g., account_create, client_add, data_list_clients). Even compound names like auth_login_with_otp adhere to this structure.

Tool Count4/5

41 tools is high but justified by the wide scope of a POS/accounting system (accounts, clients, orders, products, payments, VAT, reports). Slightly above the typical range but well-scoped.

Completeness5/5

The tool surface covers CRUD for all major entities (clients, departments, products, VAT, payment modes, orders), plus queries, reports, and authentication. No obvious gaps for a small business management server.

Resources