Skip to main content
Glama

Validate Business Discount Code

validate_community_discount_code
Read-only

Validate whether a discount code is available 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>",
      "code": "<code>"
    },
    "name": "validate_community_discount_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesDiscount code to validate.
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. Changed2 schema fields changed
    • addedInput schema / properties / code / description
      Added value: +"Discount code to validate."
    • 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.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: the FREE-tier hard block and the mandatory pre-check/grace-period flow. It still doesn't say what a validation result looks like or whether an invalid code returns an error or a false value, and there is no output schema to fall back on.

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?

Purpose is front-loaded in the first sentence, then prerequisites follow in a logical order. Several sentences are agent-behavioral instructions rather than tool semantics, which makes it heavier than necessary, but no sentence is pure filler.

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 read-only two-parameter validation tool with full schema coverage, the description covers the important preconditions and access gates. The main missing piece is return semantics, which matters because there is no output schema, but the calling contract itself is 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 100%, with both code and communityId documented, including the warning never to invent a community ID. The description adds only the business/community terminology equivalence, which the schema already implies ('Nas.com business (community) ID'), so it does not meaningfully exceed the baseline.

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 resource: 'Validate whether a discount code is available for a community.' The agent knows exactly what the tool does. However, it never distinguishes this from the sibling validate_business_discount_code; instead it says 'Business and community refer to the same thing and are interchangeable,' which leaves the two tools looking like duplicates.

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?

Gives strong contextual guidance: check business permissions first, FREE businesses cannot use it, call check_business_tool_access before collecting inputs, surface grace-period warnings and the resubscribe link, and never proceed when access is blocked. The gap is that it never says when to pick this tool over the near-identical business-named sibling.

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