Skip to main content
Glama
Sign In

Nas.com

by com.nas
OverviewDiscussionsAdmin

Update Business Stripe Connect Account

update_business_stripe_connect_account

Update Stripe Connect payout account configuration. 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>",
      "payoutAccountType": "<payoutAccountType>"
    },
    "name": "update_business_stripe_connect_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
metadataNoAdditional template settings.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
payoutAccountTypeYesType of payout account to create or update.

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 / metadata / description
      Added value: +"Additional template settings."
    • addedInput schema / properties / payoutAccountType / description
      Added value: +"Type of payout account to create or update."
  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 state readOnly=false, destructive=false, openWorld=false; the description adds real behavior beyond them, namely the permission gate, the FREE-tier exclusion, and the grace-period/resubscribe warning flow. It stops short of saying what the update actually mutates or what the call returns.

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?

Front-loaded with the purpose, then the gating rules in imperative order. Slight redundancy between 'check business permissions' and 'Call check_business_tool_access before collecting inputs', but both sentences carry actionable content.

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?

Permission gating is well covered for a mutation tool with no output schema, but payoutAccountType has no enum and the description offers no valid values or behavioral meaning, so an agent cannot construct a correct call from the definition alone. The definition also does not explain what the metadata URLs affect.

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 communityId, payoutAccountType, and the metadata sub-fields are already documented. The description only adds the business/community synonym clarification for communityId; it says nothing about valid payoutAccountType values or how returnUrl/refreshUrl are used. Baseline 3 applies when the schema carries the load.

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: 'Update Stripe Connect payout account configuration.' The note that 'Business and community refer to the same thing' clarifies terminology, but it does not distinguish this tool from the near-identical sibling update_community_stripe_connect_account, leaving the agent to guess which variant applies.

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?

Explicit preconditions: call check_business_tool_access before collecting inputs, FREE businesses cannot use it, and never proceed when access is blocked. That is strong when-not guidance and names the prerequisite sibling. What is missing is routing guidance between this tool and the community/other payout-account tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nas.com toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources