Skip to main content
Glama

Update Business Currency

update_community_currency

Update a managed community base currency. Business and community refer to the same thing and are interchangeable. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>",
      "newCurrency": "<newCurrency>"
    },
    "name": "update_community_currency"
  }
}

Input Schema

NameRequiredDescriptionDefault
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
newCurrencyYesThree-letter ISO 4217 currency code to switch the business to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / newCurrency / description
      Added value: +"Three-letter ISO 4217 currency code to switch the business to."
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare it is a non-read-only, non-destructive, closed-world mutation. The description adds substantial behavior beyond that: an entitlement gate, a hard FREE-tier exclusion, and a grace-period disclosure duty. It stops short of saying what a currency switch does to existing prices or settings, which is the main omitted behavioral fact.

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?

The access gating is front-loaded and useful, but it is stated twice: "Before offering this action or requesting its inputs, check business permissions" and "Call check_business_tool_access before collecting inputs" carry the same instruction. The terminology aside is worth keeping; the duplication is not.

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?

Prerequisite and eligibility coverage is excellent for a 2-parameter mutation with no output schema. However, it never states the consequences of the change (effect on pricing, tiers, or whether the switch is reversible), which is the one thing an agent cannot infer from the schema or annotations.

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 coverage is 100% and both parameters are documented in the schema (business/community ID sourcing rule, ISO 4217 three-letter code). The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names a specific verb and resource ("Update a managed community base currency") and immediately resolves the community/business naming ambiguity that separates this from update_business_currency. It is clear what the tool does, though it never explicitly routes the agent between the two near-identical siblings.

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?

Explicit and prescriptive: call check_business_tool_access before collecting inputs, FREE businesses are excluded regardless of feature rows, show grace-period warnings and a verified resubscribe link, and never proceed when access is blocked. This is a complete when/when-not policy with a named prerequisite tool.

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