Skip to main content
Glama

List Business Chats For CMP

list_business_chats_for_cmp
Read-only

List community chats for the community manager inbox. 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_chats_for_cmp"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoText to search for.
batchSizeNo
onlyUnreadNo
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
lastObjectIdNo

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 / search / description
      Added value: +"Text to search for."
  2. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered, yet the description adds substantial non-obvious behavior: an entitlement gate excluding FREE businesses, a mandatory pre-flight access check, and a hard stop on blocked access. This is precisely the kind of operational context annotations cannot express.

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, followed by gating requirements in a logical pre-call order. The 'Business and community refer to the same thing and are interchangeable' sentence is slightly redundant with the parenthetical '(community)' in the schema but still earns its place as a disambiguation.

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 gating is covered thoroughly, but for a paginated list tool with no output schema and only 40% parameter documentation, the definition says nothing about result shape, pagination continuation, or filtering behavior. An agent knows whether it may call the tool but not how to page through or interpret results.

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 coverage is only 40% and the description adds no meaning for any parameter — search, batchSize, onlyUnread, and lastObjectId are left entirely to the schema, and three of them have no schema description at all. It does not explain pagination semantics (batchSize/lastObjectId) or what onlyUnread's string value should be, so it fails to compensate for the coverage gap.

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?

States a specific verb and resource ('List community chats') plus the scope ('for the community manager inbox') and clarifies the business/community synonym, which prevents a naming confusion. It does not, however, distinguish itself from the similarly named sibling list_community_chats_for_cmp, so an agent must guess which of the two listers to call.

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?

Explicit when-not-to-use rules are given: FREE businesses cannot use the tool regardless of feature rows, and it must not proceed when access is blocked. It names the prerequisite tool (check_business_tool_access) and the exact ordering ('before collecting inputs', 'before offering this action'), plus required UX steps around grace-period warnings.

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