Nas.com MCP

Record CMP Visit

record_cmp_visit

Record a community manager visit marketing event. 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
`communityId`	Yes

TDQS

A4.6/5.0

Behavior5/5

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

Discloses important behavioral traits beyond annotations: the tool is not available for FREE businesses, requires prior access check, and has UI interaction requirements. Annotations (readOnlyHint=false, destructiveHint=false) are not contradicted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is concise with 5 sentences, front-loaded with the action, then clearly states conditions and prerequisites. No unnecessary words.

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

Completeness5/5

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

For a tool with 1 required parameter, no output schema, and no nested objects, the description covers all essential context: permissions, business restrictions, prerequisites, and UI behavior. It is complete for an agent to use correctly.

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

Parameters2/5

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

Schema has 1 parameter (communityId) with 0% description coverage. The description does not explain what communityId represents or any additional context for its value. Parameter meaning is left to inference from the name, which is insufficient compensation for low coverage.

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?

The description clearly states the action ('Record') and the resource ('a community manager visit marketing event'). It is a specific verb+resource combination that distinguishes it from sibling tools.

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?

Explicitly provides when to use (after checking permissions, not for FREE businesses) and prerequisites (call check_business_tool_access before collecting inputs, show grace-period warning and resubscribe link). Clearly states when not to proceed.

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?