Skip to main content
Glama
Sign In

Nas.com

by com.nas
OverviewDiscussionsAdmin

Get Whatsapp Business Member

get_whatsapp_community_member
Read-only

Get a WhatsApp community member by WhatsApp ID. 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>",
      "whatsappId": "<whatsappId>"
    },
    "name": "get_whatsapp_community_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
whatsappIdYesWhatsApp member record ID.
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 / whatsappId / description
      Added value: +"WhatsApp member record ID."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, so the bar is lower. The description adds real behavioral context the annotations cannot express: plan-level access gating, a mandatory access-check step, and the requirement to surface grace-period warnings and a verified resubscribe link. It omits what a 'member' record contains, but no output schema exists either.

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?

Purpose is front-loaded in the first sentence, followed by the naming clarification and then the access-gating steps in the order they must be performed. No sentence is filler, and the repetitiveness about blocked access is reinforcing a hard constraint rather than padding.

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 tool with full schema coverage, closed-world and read-only annotations, the description covers purpose, inputs, and the access preconditions an agent must honor. The only gap is the return shape, which no output schema defines, but that is minor for a simple getter.

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%, so both parameters are fully documented in the schema, including the warning not to invent a communityId. The description's statement that 'business and community refer to the same thing' usefully disambiguates the communityId naming, but otherwise adds no syntax or format detail beyond the schema.

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 opens with a specific verb+resource: 'Get a WhatsApp community member by WhatsApp ID.' It also resolves the business/community naming ambiguity, which matters because siblings like get_whatsapp_business_member and get_business_member exist under the other name. It stops short of stating explicitly why an agent would pick this over the parallel business-named retrieval tool.

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?

Unusually explicit about preconditions: check business permissions, call check_business_tool_access before collecting inputs, never proceed when access is blocked. It gives a clear when-not (FREE businesses cannot use this tool regardless of feature rows). It does not, however, say when to use this vs. sibling retrieval tools such as get_business_member or get_community_member.

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

All Nas.com toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources