Skip to main content
Glama

Check Business Summary Exists

check_community_summary_exists
Read-only

Check whether a community monthly summary exists. 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>",
      "month": "<month>",
      "year": "<year>"
    },
    "name": "check_community_summary_exists"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesFour-digit calendar year.
monthYesCalendar month, 1-12.
timezoneNoIANA time zone, for example Asia/Singapore.
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. Changed4 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 / month / description
      Added value: +"Calendar month, 1-12."
    • addedInput schema / properties / timezone / description
      Added value: +"IANA time zone, for example Asia/Singapore."
    • addedInput schema / properties / year / description
      Added value: +"Four-digit calendar year."
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive profile, and the description adds gating behavior the annotations cannot express: entitlement checks, grace-period warnings, resubscribe links, and a mandatory halt on blocked access. It does not describe what the check returns (boolean vs. an object with summary metadata), which is the only remaining behavioral gap.

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 rest is ordered as terminology, then prerequisites, then stop conditions. The terminology and permission sentences are somewhat repetitive, but each carries operational weight for an agent deciding whether to call.

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 read-only existence check with fully documented parameters and no output schema, the definition covers purpose, prerequisites, and blocking conditions adequately. The one omission is the expected return shape, which matters when the whole tool is a boolean-style query.

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%, so year, month, timezone, and communityId are already documented with formats and constraints. The description adds no syntax or format detail beyond reinforcing that community means business, so the baseline of 3 applies.

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

Purpose5/5

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

States a specific verb and resource ("Check whether a community monthly summary exists") and immediately resolves the naming ambiguity by declaring business and community interchangeable, which is exactly the distinction an agent needs against the sibling check_business_summary_exists.

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?

Gives explicit preconditions (call check_business_tool_access before collecting inputs), a hard exclusion (FREE businesses cannot use this tool regardless of feature rows), and a proceed/stop decision rule when access is blocked. This is the when/when-not pattern at full strength.

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