Skip to main content
Glama

List Business Members For Admin

list_business_members_for_admin
Read-only

Call the legacy manager memberships-for-admin route. 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>"
    },
    "name": "list_business_members_for_admin"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. Changed1 schema field 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."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare a safe, closed read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description does add real context: this is a legacy route and it is hard-blocked for FREE businesses. However, it never discloses what the operation returns or whether results are paginated, which is the behavior an agent most needs after the access gate.

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 compliance boilerplate dominates while the actual purpose is compressed into a vague first clause about a "legacy route." Sentences are individually clear, but the useful content (purpose, return shape) is buried behind access-gating instructions.

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?

Access prerequisites are covered thoroughly, which suits a gated admin tool with no output schema. But for a read-only single-param list operation, the description omits any sense of result contents or size, so an agent knows whether it may call but not what it will get back.

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?

With a single parameter at 100% schema coverage, the schema already explains communityId and warns against inventing IDs. The only added semantic is that business and community are interchangeable, which the schema itself already states, so no meaning is contributed beyond the structured field.

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

Purpose3/5

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

The description says to "call the legacy manager memberships-for-admin route," which gestures at listing members via an admin route but never plainly states the verb+resource (e.g. "list the members of a business"). It clarifies the business/community synonym, but an agent must lean on the tool name to know what the call actually returns.

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?

Strong, explicit gating: check business permissions before offering the action, call check_business_tool_access before collecting inputs, FREE businesses cannot use it regardless of feature rows, and never proceed when access is blocked. What's missing is differentiation from near-siblings such as list_community_members_for_admin or list_members, since no alternative is named.

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