Skip to main content
Glama

Update Business Discount

update_business_discount

Update active state for a community discount. 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>",
      "discountId": "<discountId>"
    },
    "name": "update_business_discount"
  }
}

Input Schema

NameRequiredDescriptionDefault
isActiveNoWhether the item is active immediately.
discountIdYesDiscount code ID, from the discount listing.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.

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 / discountId / description
      Added value: +"Discount code ID, from the discount listing."
    • addedInput schema / properties / isActive / description
      Added value: +"Whether the item is active immediately."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=false; the description adds substantial context beyond them — a mandatory access-gate tool call, the FREE-tier hard block, grace-period warnings, and a verified resubscribe link requirement. It doesn't explain the effect of deactivating an already-redeemed discount or what the response contains, leaving a small behavioral gap for a mutation.

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?

Front-loaded with the action and appears complete, but it says the same thing twice: 'Before offering this action or requesting its inputs, check business permissions' and 'Call check_business_tool_access before collecting inputs.' The later sentences about grace-period warnings and the resubscribe link are procedural UI instructions that dilute the core tool semantics, so the text is longer than needed.

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 gated toggle, the description covers the access prerequisites, the tier restriction, and the blocked-path behavior that an agent could otherwise get wrong. The only real omission is the return value or confirmation behavior, which matters somewhat given there is no output schema.

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 communityId, discountId and isActive are already documented with formats and sourcing guidance in the schema. The description only echoes 'active state' and adds no semantics on defaults, idempotency, or what happens when isActive is omitted. Baseline 3 is appropriate.

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?

States a specific verb and scope: 'Update active state for a community discount,' which tells the agent this toggles isActive rather than editing other discount fields. The sentence 'Business and community refer to the same thing and are interchangeable' usefully explains the naming split versus the update_community_discount / update_business_discount siblings, though it doesn't explicitly say which one to prefer in a given context.

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?

Gives explicit preconditions and exclusions: check business permissions, call check_business_tool_access before collecting inputs, and never proceed when access is blocked. It names a hard exclusion ('FREE businesses cannot use this tool, regardless of individual feature rows'), which is exactly the kind of when-not guidance an agent needs before attempting the call.

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