Skip to main content
Glama

Get Business Discount

get_business_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_business_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. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: plan-tier blocking, a permission-check tool that must be called first, grace-period warnings and a verified resubscribe link, and the instruction never to proceed when access is blocked. It still says nothing about error shape or what happens with an invalid/expired discount ID.

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 correctly front-loaded in the first sentence, but the remainder is a dense wall of access-control instructions. There is redundancy between 'Before offering this action or requesting its inputs, check business permissions' and 'Call check_business_tool_access before collecting inputs', plus a trailing 'never proceed when access is blocked' that restates the same constraint a third time.

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?

For a two-parameter read tool with full schema coverage and read-only annotations, the access/prerequisite workflow is thoroughly covered. What is missing is any indication of what the call returns (no output schema exists) and any routing guidance relative to the near-identical get_community_discount sibling. Adequate, but with clear gaps.

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%, with both discountId and communityId fully documented including provenance ('from the discount listing', 'use an ID returned by list_businesses ... never invent one'). The description adds no meaning beyond that; its only input-related content is a sequencing rule ('call check_business_tool_access before collecting inputs'). 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?

The opening sentence gives a specific verb and resource: 'Get details for one community discount.' The follow-up clause 'Business and community refer to the same thing and are interchangeable' usefully disambiguates the naming overlap with siblings like get_community_discount. However, it never states which sibling to prefer for retrieving a discount, so 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-not condition (FREE businesses cannot use this tool, regardless of individual feature rows) and a mandatory prerequisite (call check_business_tool_access before collecting inputs). That is stronger gating guidance than most definitions provide. The gap is that no alternative retrieval tool is named for the actual 'get discount details' task.

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