Skip to main content
Glama

Get Business Discount

get_community_discount
Read-only

Get details for one 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": "get_community_discount"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. 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 / discountId / description
      Added value: +"Discount code ID, from the discount listing."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds access-control behavior not present in structured fields, such as plan-tier gating, the permissions precheck, and the grace-period warning plus verified resubscribe link. These are real operational constraints an agent would otherwise violate.

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 and the interchangeability note are front-loaded, and every sentence carries an actionable constraint. There is mild redundancy between "check business permissions" and "Call check_business_tool_access" plus the repeated blocking warning, which costs a point.

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 two-parameter read with full schema coverage and no output schema, the access-gating context is unusually thorough. The remaining gap is that it never hints at what "details" are returned, so an agent cannot anticipate payload shape before calling.

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 already carry descriptions covering provenance (discountId from the discount listing, communityId from list_businesses, never invented). The description adds no further meaning about the two inputs, so the baseline of 3 is correct.

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

Purpose5/5

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

"Get details for one community discount" names a specific verb, resource, and cardinality (single record). The follow-up sentence resolves the business/community naming ambiguity, which lets an agent distinguish this from get_business_discount in the sibling list.

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 names the prerequisite tool explicitly ("Call check_business_tool_access before collecting inputs") and states a hard exclusion: FREE businesses cannot use this tool regardless of individual feature rows. It also gives a stop condition — never proceed when access is blocked — so there is no inference required about when to use versus abort.

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