Skip to main content
Glama

List Business Referees

list_business_referees
Read-only

List referred communities/referees for a managed community. 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": "list_business_referees"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number to return, starting at 1.
sortByNoField to sort results by.
statusNoStatus value; use one of the allowed values in this schema.
pageSizeNoNumber of results per page.
sortOrderNoSort direction for the results.
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. Changed6 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 / pageNo / description
      Added value: +"Page number to return, starting at 1."
    • addedInput schema / properties / pageSize / description
      Added value: +"Number of results per page."
    • addedInput schema / properties / sortBy / description
      Added value: +"Field to sort results by."
    • addedInput schema / properties / sortOrder / description
      Added value: +"Sort direction for the results."
    • addedInput schema / properties / status / description
      Added value: +"Status value; use one of the allowed values in this schema."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish that this is a non-destructive read-only operation. The description adds meaningful operational context beyond the annotations, including permission checks, FREE-business exclusion, grace-period warnings, and resubscribe links. It does not describe return format or pagination behavior, though the schema covers pagination inputs.

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 description is front-loaded with the purpose and then moves into access rules. Most sentences are operationally necessary, but there is some redundancy between "Before offering this action or requesting its inputs, check business permissions" and "Call check_business_tool_access before collecting inputs."

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 listing tool with no output schema, the description covers the important access constraints and prerequisites needed to invoke it correctly. It does not explain the returned referee fields or pagination behavior, but those are relatively minor for this tool type.

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 the input schema already documents all six parameters, including allowed enum values and constraints. The description adds no parameter-specific meaning beyond the schema. A baseline score of 3 is appropriate when the schema carries this responsibility.

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 uses a specific verb and resource: "List referred communities/referees for a managed community." It also clarifies that "business" and "community" are interchangeable, which reduces naming ambiguity. However, it does not explicitly distinguish this tool from the similarly named sibling list_community_referees.

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?

It gives clear prerequisite and exclusion guidance: check business permissions, call check_business_tool_access before collecting inputs, and never proceed when access is blocked. It also explicitly excludes FREE businesses. The main gap is that it does not state when to use this tool rather than a sibling listing tool.

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