Skip to main content
Glama

Get Business Member Activity

get_business_member_activity
Read-only

Get merged activity logs for one member in 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.

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>",
      "membershipId": "<membershipId>"
    },
    "name": "get_business_member_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
membershipIdYesMembership ID of the member, from a Nas.com member listing.

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 / membershipId / description
      Added value: +"Membership ID of the member, from a Nas.com member listing."
  2. First observed

TDQS

A3.8/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 semantics, and the description adds genuinely new gating behavior: entitlement checks, tier-based exclusion, grace-period surfacing, and an explicit "never proceed when access is blocked" rule. It does not describe what "merged" logs actually contain or their volume/ordering, which is the main remaining behavioral unknown.

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?

Purpose and vocabulary disambiguation are front-loaded in the first two sentences, with the access-gating procedure following in a logical order. It is slightly dense with imperative instructions, but each sentence carries a distinct operational rule rather than filler.

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, and the two required parameters are fully documented. However, with no output schema present, the description never explains what a member activity log returns (event types, ordering, truncation), leaving the agent unable to anticipate the response shape of the tool it is being told to gate so carefully.

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%, and both parameters carry their own descriptions including provenance guidance (use IDs from list_businesses, never invent one). The tool description adds no parameter-level meaning beyond that, so the baseline 3 applies with the schema doing the heavy lifting.

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?

"Get merged activity logs for one member in a managed community" gives a specific verb, resource, and scope, and it additionally resolves the business/community vocabulary ambiguity. It stops short of distinguishing itself from the near-identical sibling get_community_member_activity, so the agent must infer the difference from the name alone.

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 on exclusions and prerequisites: it names FREE businesses as an ineligible cohort, directs the agent to call check_business_tool_access before collecting inputs, and requires surfacing grace-period warnings. What is missing is any statement about when to pick this over the sibling get_community_member_activity, so routing between the two look-alike tools is left to inference.

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