Skip to main content
Glama

sales_settings_upsert

Idempotent

[REQUIRES APPROVAL] Saves your business identity and document defaults (one row per business; scope is 'default'). timezone is the business clock: an invoice turns overdue at midnight in that zone after its due day, and days_overdue counts days there; unset means Asia/Singapore. Left out, timezone and the text fields keep their saved value, but defaulted fields (default_currency, default_tax_rate_bps, payment_terms_days, invoice_prefix, quote_prefix, template_style) reset, so resend them from sales_settings_read. An agent call waits for the owner's approval. Refuses an unlisted timezone or currency, or a tax rate outside 0-10000, with VALIDATION_ERROR before it waits for approval: send a listed value.

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": {
      "scope": "<scope>"
    },
    "name": "sales_settings_upsert"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeYes
tax_idNo
timezoneNo
bank_nameNo
tax_schemeNo
bank_accountNo
quote_prefixNo
business_nameNo
business_emailNo
business_phoneNo
invoice_prefixNo
template_styleNo
business_addressNo
default_currencyNo
brand_accent_colorNo
payment_terms_daysNo
brand_primary_colorNo
default_tax_rate_bpsNo
payment_instructionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior1/5

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

The annotations declare destructiveHint=false, but the description states that omitted defaulted fields reset to defaults, overwriting previously saved values. That is a destructive update to existing settings, making the description contradict the annotation despite otherwise useful disclosure of approval and validation behavior.

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 dense but front-loads the approval requirement and core purpose, then moves through timezone semantics, reset behavior, approval timing, and validation. Every sentence carries operational information relevant to invoking the tool correctly.

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?

Given the mutation complexity, approval requirement, 19 parameters, and absence of an output schema, the description covers the most important behavioral details. However, it does not state what is returned after approval or explain several parameters, so it is not fully complete.

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 0% across 19 parameters. The description adds important meaning for timezone, default-reset behavior, and tax/currency validation, but leaves many parameters such as tax_scheme, bank details, brand colors, and payment_instructions without added semantics beyond their names and enums.

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 states a specific verb and resource: saving business identity and document defaults, with one row per business and scope 'default'. It also implicitly distinguishes itself from sales_settings_read by telling the agent to resend defaulted fields from that sibling.

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?

It explains that calls wait for owner approval, that validation errors occur before approval, and that omitted defaulted fields should be resent from sales_settings_read. It does not explicitly compare against siblings such as sales_settings_numbering_set or state when not to use this tool, but the operational context is clear.

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