Skip to main content
Glama

Has Unread Business Chat

has_unread_business_chat
Read-only

Check whether a managed community has unread chat messages. 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": "has_unread_business_chat"
  }
}

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

A3.8/5.0
Behavior4/5

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

Annotations already establish a safe, closed-world read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's real contribution is the entitlement gating: plan-level blocking, a mandatory pre-check via check_business_tool_access, and the grace-period/resubscribe flow. That is meaningful behavior an agent could not infer from the annotations. It stops short of saying what the call returns (a boolean flag) or what happens on a blocked call.

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 purpose is front-loaded correctly, but the gating instructions are stated twice in near-identical form ('check business permissions ... before requesting its inputs' and 'Call check_business_tool_access before collecting inputs'). Five sentences for a one-parameter boolean check is heavier than needed, and the repetition costs readability.

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 single-parameter read-only predicate with no output schema, the description covers the hard part: entitlement checks and the required ordering of calls. The notable omission is the return value's shape, which the agent must guess since no output schema exists.

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?

There is a single parameter at 100% schema description coverage, and the schema already explains communityId, including the 'never invent one, use list_businesses' constraint. The description adds nothing about the parameter beyond restating that business and community are interchangeable. Baseline 3 applies since the schema carries the semantics.

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 first sentence gives a specific verb and resource: check whether a managed community has unread chat messages. It also equates 'business' and 'community', which preempts confusion with siblings like has_unread_community_chat. It does not distinguish itself from has_new_unread_business_chat or has_new_unread_community_chat, so an agent must still infer the 'new' variant difference.

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?

Provides explicit when-not-to-use conditions: FREE businesses cannot use it regardless of feature rows, and the agent must call check_business_tool_access before collecting inputs and must never proceed when access is blocked. The only gap is that it names no alternative tool for the cases where this one is disallowed.

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