Skip to main content
Glama

List Business Activities

list_business_activities
Read-only

List recent activity feed items 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.

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_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
activityTypesNo
lastActivityObjectIdNo

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 / limit / description
      Added value: +"Maximum number of results to return."
  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 readOnly/closed/non-destructive, and the description adds substantive non-obvious behavior: entitlement gating, ineligibility for FREE businesses, grace-period warnings, a verified resubscribe link, and a hard stop on blocked access. It does not describe result ordering, recency window, or pagination behavior of the feed, which is why it falls short of a 5.

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 is front-loaded in the first sentence and the gating rules follow in a logical order. The access-check instruction is stated twice in slightly different words ("Before offering this action... check business permissions" and "Call check_business_tool_access before collecting inputs"), which is mild redundancy but also reinforces a safety-critical step.

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?

With no output schema, the description should convey what a returned activity feed item contains or how many/which are returned, and it does not. Combined with two undocumented parameters, the agent can call the tool but cannot predict or interpret results beyond 'recent activity items'; the access-gating coverage is strong, but the data-shape coverage is thin.

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 50%: communityId and limit are documented in the schema, while activityTypes and lastActivityObjectId have no description anywhere. The description does add meaning for communityId by explaining that business and community are interchangeable, but it says nothing about accepted activity types or what an activity object ID refers to.

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 gives a specific verb and resource ("List recent activity feed items for a managed community") and clarifies the business/community synonym, which prevents confusion given the tool name says 'business' while the required key is 'communityId'. It does not distinguish this from the near-identical sibling list_community_activities, so the agent gets no routing signal between the two.

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?

It states explicit preconditions and ordering (call check_business_tool_access before collecting inputs, before offering the action), a hard exclusion (FREE businesses cannot use this tool regardless of feature rows), and a blocking rule (never proceed when access is blocked). The agent knows both when to use it and when to stop.

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