Skip to main content
Glama

Get Business Analytics Graph

get_business_analytics_graph
Read-only

Get graph datapoints for community analytics. 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": "get_business_analytics_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
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

A4/5.0
Behavior5/5

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

Annotations only declare readOnly/non-destructive/non-open-world; the description adds substantive behavior the annotations cannot convey — entitlement gating, tier-based denial for FREE businesses, and a mandatory pre-flight access check with a hard stop condition. This is exactly the extra context that prevents a doomed 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?

Purpose is front-loaded and the access rules are actionable, but the permission guidance is restated twice ('check business permissions before offering this action' and 'Call check_business_tool_access before collecting inputs'). The description also spends its entire length on access gating while saying nothing about the data being fetched.

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 analytics endpoint with no output schema, the definition covers the highest-risk failure mode (entitlement denial) thoroughly. The remaining gap is that it never describes what the graph datapoints look like or what 'days' controls, leaving the caller blind on result shape.

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 50%: communityId is fully documented in the schema, but 'days' has no description anywhere. The description never mentions the time-window parameter, its units, defaults, or how the range affects the returned graph, 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 ('Get graph datapoints for community analytics') and resolves the business/community vocabulary ambiguity up front. It does not, however, differentiate itself from the sibling get_community_analytics_graph or get_business_analytics_graph variants, so an agent still has to guess which graph endpoint to use.

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-to-use gating: check business permissions before offering the action, call check_business_tool_access before collecting inputs, and never proceed when access is blocked. It also names the excluded case (FREE businesses cannot use this tool regardless of feature rows) and the UX requirement around the grace-period warning and resubscribe link.

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