Nas.com MCP

List Business Discounts

list_business_discounts

Read-only

List discounts for a managed 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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pageNo`	No
`search`	No
`sortBy`	No
`status`	No
`pageSize`	No
`sortOrder`	No
`entityType`	No
`communityId`	Yes
`excludeEmptyEntities`	No

TDQS

A3.8/5.0

Behavior5/5

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

Annotations indicate read-only and non-destructive behavior. The description adds important preconditions and restrictions (FREE businesses blocked, need to check access, show warnings), providing context beyond the annotations.

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 description is concise and front-loads the purpose, but the procedural steps could be better organized. Overall, it's efficient with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While preconditions are well-covered, the description omits all parameter semantics for a tool with 9 parameters and no output schema. This leaves the agent with insufficient context to correctly invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides no information about the 9 parameters (pageNo, search, sortBy, etc.). With 0% schema description coverage, the agent has no guidance on how to populate these parameters.

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 states 'List discounts for a managed community,' which is clear. However, it does not differentiate from sibling tool 'list_community_discounts,' and the interchangeability of 'business' and 'community' could cause confusion.

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 guidance is provided: check permissions, FREE businesses cannot use, call check_business_tool_access first, show grace-period warning and resubscribe link, never proceed if blocked. This clearly tells the agent when and how to use the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nas.com MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3/5.0

Disambiguation2/5

Many tools are semantically identical, distinguished only by 'business' vs 'community' prefixes, and descriptions explicitly state they are interchangeable. This creates ambiguity for agent selection. Examples include add_business_admins/add_community_admins and get_business/get_community.

Naming Consistency3/5

Tools generally follow a verb_noun pattern, but the inconsistent use of 'business' vs 'community' for the same entities breaks the pattern. While individual naming is clear, the overall set lacks uniformity.

Tool Count1/5

With 423 tools, the server is massively over-scoped. The high count is driven by redundant 'business' and 'community' variants and many niche operations. A more focused surface would be far more manageable.

Completeness4/5

The tool set covers a broad range of features including CRUD operations for multiple product types, analytics, payments, messaging, and integrations. Minor gaps exist (e.g., missing update for some entity types), but overall domain coverage is strong.

Resources

Need Help?