Skip to main content
Glama

Get Business Payout Account

get_business_payout_account
Read-only

Get payout account configuration 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": "get_business_payout_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: tier-gating (FREE blocked), permission precheck, and a required grace-period warning flow. It omits what the returned configuration actually contains, which matters since there is no output schema.

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?

Purpose is front-loaded in the first sentence, followed by constraints in priority order. Some redundancy: the permission check is stated twice ("Before offering this action... check business permissions" then "Call check_business_tool_access before collecting inputs"), and the UI-warning sentence is dense procedural detail that could be tightened.

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 one-parameter read tool with full schema coverage and no output schema, the gating and prerequisite behavior is well covered. The main gap is the absence of any indication of what the payout account configuration contains, which an agent cannot recover from structured fields here.

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 100% and the single communityId parameter is already documented in-schema, including the instruction to source it from list_businesses and never invent one. The description's only added semantic is that business and community are interchangeable, which the schema also conveys. Baseline 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?

"Get payout account configuration for a managed community" states a specific verb (get) and resource (payout account configuration) plus its scope. It does not name the create/delete siblings, but the read vs. mutate distinction is obvious from the verb. The community/business equivalence note resolves naming ambiguity.

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?

Gives an explicit prerequisite (call check_business_tool_access before collecting inputs) and an explicit exclusion (FREE businesses cannot use it, even if feature rows say otherwise; never proceed when access is blocked). It stops short of naming the sibling read variants, but the when-to-use and when-not conditions are both stated.

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