Skip to main content
Glama

Get Business Permissions

get_community_permissions
Read-only

Get feature permissions for a managed community, optionally including usage. Business and community refer to the same thing and are interchangeable.

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_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
includeUsageNo

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one real behavioral fact beyond that: results can optionally include usage data via includeUsage. It says nothing about authorization requirements or what a 'feature permission' record contains.

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?

Two short sentences, with the core purpose front-loaded before the terminology note. The second sentence earns its place as a terminology disambiguator, though it slightly muddies things given the get_business_permissions sibling rather than resolving the relationship.

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 two-parameter read tool with full annotations and no output schema, this is close to sufficient: the agent knows it reads feature permissions for one required community ID and can optionally pull usage. The remaining gap is that the shape of the returned permission set is never hinted at.

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 50%: communityId is fully documented in the schema (including the 'never invent one' warning), but includeUsage has no schema description at all. The description partially compensates by framing it as 'optionally including usage', implying it is a non-required enrichment flag, but does not explain what usage data means or what its absence omits.

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 names a specific verb and resource: 'Get feature permissions for a managed community'. It also disambiguates terminology ('Business and community refer to the same thing'), which matters because a sibling is named get_business_permissions. It stops short of distinguishing this tool from that similarly named sibling, so the agent must guess which one applies to a given business ID.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Nothing says when to call this versus get_business_permissions or list_feature_plan_permissions, which are the two most plausible alternatives. There are no prerequisites, no exclusions, and no indication of what 'including usage' costs or changes for the caller.

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