Skip to main content
Glama

List Business Payouts

list_business_payouts
Read-only

List payouts 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_payouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number to return, starting at 1.
pageSizeNoNumber of results per page.
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. Changed3 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."
  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 and destructiveHint=false, and the description adds real behavioral context beyond them: an access-check precondition, an entitlement-based exclusion, and instructions to surface grace-period warnings and a verified resubscribe link. It stops short of describing result contents or pagination behavior, but the access-gating detail is substantive.

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 in the first sentence, but the access-gating instructions are repetitive: 'Before offering this action or requesting its inputs, check business permissions' and 'Call check_business_tool_access before collecting inputs' convey the same rule twice, bloating an otherwise short definition.

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 paged list tool with full schema coverage and safety annotations, this is largely complete: an agent knows the entity scope, the permission gate, and the blocking conditions. The main omission is any guidance on choosing between this and list_community_payouts, plus nothing about what a payout record contains.

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 pageNo, pageSize, and communityId are already fully documented. The description adds no further parameter meaning, such as default page size or ordering of payouts, so the baseline of 3 applies.

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 ("List payouts for a managed community") and clarifies that 'business' and 'community' are interchangeable, which explains the naming. It does not, however, distinguish this from the sibling list_community_payouts, whose name suggests an equivalent operation.

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?

Explicitly names a prerequisite tool (check_business_tool_access), states a hard exclusion (FREE businesses cannot use it regardless of feature rows), and specifies ordering (check access before collecting inputs or proceeding). The only gap is that it never says when to prefer list_community_payouts over this 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