Skip to main content
Glama

Update Business Chat Settings

update_community_chat_settings

Update chat availability and welcome settings for a community. 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>"
    },
    "name": "update_community_chat_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
isEnabledNo
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
responseTimeNo
welcomeMessageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare it is a non-readonly, non-destructive, closed-world mutation, so the safety profile is partly covered. The description adds genuinely non-structured context: plan-tier gating, a required pre-flight access check, grace-period warnings, and a hard stop when access is blocked. What it does not disclose is update semantics — whether omitted fields are left untouched, whether responseTime can be cleared with null, or what the tool returns.

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 purpose is front-loaded and the access-gating rules are clear, but the permission requirement is stated twice in near-identical wording ('Before offering this action or requesting its inputs, check business permissions' and 'Call check_business_tool_access before collecting inputs'). The repetition costs space that could have documented responseTime or welcomeMessage constraints.

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?

With no output schema and only 25% schema coverage, the description carries the burden for four parameters and the return behavior, and it addresses neither well. It is thorough on access gating, which is the highest-risk aspect of the call, but an agent still cannot tell what responseTime means or whether partial updates are supported. Adequate for avoiding a permission error, incomplete for actually invoking the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%: communityId is documented in the schema and reinforced in the description's chat-settings framing, but isEnabled and welcomeMessage are only obliquely implied by 'availability and welcome settings.' The responseTime object (frequencyUnit/frequencyCount) is undocumented in both the schema and the description, which is exactly the kind of gap low coverage requires the description to fill.

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 opening sentence gives a specific verb and resource plus the affected fields: 'Update chat availability and welcome settings for a community.' The sentence clarifying that 'Business and community refer to the same thing' usefully disambiguates this tool from the near-identical update_business_chat_settings sibling. However, it never distinguishes this from update_community_chat_status, which sits right alongside it in the catalog, so the sibling differentiation is only partial.

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?

It states explicit preconditions and exclusions: check business permissions, call check_business_tool_access before collecting inputs, FREE businesses cannot use the tool 'regardless of individual feature rows', show any grace-period warning and verified resubscribe link, and 'never proceed when access is blocked.' It also names the prerequisite sibling tool to call. The only gap is the absence of guidance on when to pick this over update_community_chat_status, but the when/when-not routing is otherwise unusually explicit.

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