Skip to main content
Glama

Check Business Summary Exists

check_business_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_business_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. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed world, so safety is covered. The description adds genuinely non-obvious behavior: FREE-tier accounts are blocked regardless of feature rows, and a grace-period warning plus verified resubscribe link must be surfaced before continuing. What it does not disclose is the return shape, though 'check whether ... exists' strongly implies a boolean.

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 core purpose is front-loaded in the first sentence, which is good. However, more than half the text is procedural workflow instruction (show warning, show resubscribe link, never proceed) rather than tool-purpose content, and the 'business and community are interchangeable' note adds length without much operational value.

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 4-parameter read-only existence check with full schema coverage and no output schema, the description covers the important risks: permission gating, tier restriction, and blocked-access handling. The only gap is what the tool returns when access is allowed, which the name largely implies.

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 description coverage is 100%, so communityId, month, year and timezone are already documented in the schema. The description adds no parameter-level meaning at all, including none of the month/year/timezone scoping that determines which summary is checked. Baseline 3 applies when the schema does 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?

The description states a specific verb and resource: 'Check whether a community monthly summary exists.' An agent can tell this is an existence check rather than a data fetch. It does not differentiate itself from near-identical siblings such as check_community_summary_exists or get_business_summary, leaving that inference to the caller.

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 precondition guidance: check business permissions first, FREE businesses cannot use the tool regardless of feature rows, and check_business_tool_access must be called before collecting inputs. It stops short of naming when to prefer this over sibling existence/summary tools, so it is clear context without alternatives.

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