Skip to main content
Glama

Update Business Notification Preference

update_business_notification_preference

Update the current user notification preference for a community trigger. 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>",
      "triggerName": "<triggerName>",
      "notificationEnabled": "<notificationEnabled>"
    },
    "name": "update_business_notification_preference"
  }
}

Input Schema

NameRequiredDescriptionDefault
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
triggerNameYesNotification trigger to update.
notificationEnabledYesWhether the notification is turned on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / notificationEnabled / description
      Added value: +"Whether the notification is turned on."
    • addedInput schema / properties / triggerName / description
      Added value: +"Notification trigger to update."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations declare a non-destructive write inside a closed world, and the description goes well beyond that by disclosing the entitlement gate, a mandatory pre-flight check, and required user-facing disclosures such as grace-period warnings. It reveals behavior the agent could not infer from the schema or annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition leads with the action, then stacks the gating rules in a logical order. There is mild redundancy between 'Before offering this action... check business permissions' and 'Call check_business_tool_access before collecting inputs,' which restates the same precondition twice in adjacent sentences.

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?

For a three-parameter, non-destructive mutation with a fully covered schema, the description covers the hard part: entitlement gating and the required pre-flight tool call. It does not describe the outcome of a successful update, but with no output schema and a simple boolean toggle, that omission is minor.

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%, so all three parameters are already documented, including the communityId guidance about using an ID from list_businesses. The description adds only the framing that business and community are interchangeable, which marginally helps with communityId but adds nothing for triggerName or notificationEnabled. Baseline 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 description uses a specific verb and resource: 'Update the current user notification preference for a community trigger.' It also resolves the business/community terminology ambiguity, which is genuinely useful given sibling tools like update_community_notification_preference exist. It stops short of explicitly contrasting itself with that sibling, so it doesn't fully earn a 5.

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 preconditions and exclusions: FREE businesses cannot use it regardless of feature rows, and check_business_tool_access must be called before collecting inputs. It also tells the agent to surface grace-period warnings and verified resubscribe links, and to abort when access is blocked. This is exactly the when/when-not/prerequisite guidance the dimension asks for.

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