Skip to main content
Glama

Get Business Analytics Graph

get_community_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_community_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. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false) and the description is consistent with them. It adds genuine behavioral context beyond the annotations: FREE-tier businesses are hard-blocked regardless of feature rows, and access must be verified via check_business_tool_access with a grace-period warning surfaced. However, it says nothing about the return payload, pagination, or what 'graph datapoints' look like.

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?

The purpose is front-loaded and the gating instructions follow in logical order. There is mild redundancy between 'Before offering this action or requesting its inputs, check business permissions' and 'Call check_business_tool_access before collecting inputs', which restate the same prerequisite twice, but no filler otherwise.

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-control behavior is thoroughly documented, which is the highest-risk area for this tool. With no output schema, the description should explain what a 'graph datapoint' is and what 'days' controls; it does neither, leaving an agent unable to predict or validate the response.

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 documented in the schema, but the 'days' integer (exclusiveMinimum 0) has no description anywhere. The description never mentions 'days' — no default, no granularity, no effect on the returned series — so the second parameter remains ambiguous and the description does not 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.' It also resolves a real naming ambiguity by declaring that business and community are interchangeable, which matters given the title says 'Business Analytics Graph'. It does not distinguish this tool from close siblings such as get_community_analytics or get_business_analytics_graph, so an agent cannot tell from the text which one yields graph datapoints versus raw analytics.

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 on prerequisites: check business permissions, call check_business_tool_access before collecting inputs, never proceed when access is blocked, and surface the grace-period warning and resubscribe link. What is missing is sibling routing — there is no statement of when to prefer this over get_community_analytics, get_community_analytics_v2, or get_business_analytics_graph.

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