Skip to main content
Glama

Get Payment Fee Rate

get_payment_fee_rate
Read-only

Get payment fee rate for a community purchase type. 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_payment_fee_rate"
  }
}

Input Schema

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

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.8/5.0
Behavior4/5

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

Annotations already declare this a safe, non-destructive read, so the bar is lower; the description still adds real operational context — a mandatory access check, a hard block for FREE businesses, and required grace-period warning and resubscribe link handling. It says nothing about the shape of the returned fee rate, which matters somewhat given 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 and the gating rules follow in a logical order. There is mild redundancy between "check business permissions" and "Call check_business_tool_access," but no sentence is wasted.

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?

For a simple two-parameter read tool the access-gating rules are thorough, but the description leaves purchaseType's allowed values undefined and gives no indication of what the returned fee rate contains (rate value, currency, tier?). An agent can call it correctly only if it already knows the purchase type vocabulary.

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 well documented in the schema while purchaseType has no description or enum anywhere. The phrase "community purchase type" hints that purchaseType drives the lookup, but the description does not enumerate valid purchase types or defaults, so it only partially compensates for the gap.

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 payment fee rate for a community purchase type" gives a specific verb and resource with a stated scope (community + purchase type). It does not explicitly differentiate itself from lookalike siblings such as get_processing_fee_preference or get_unified_plan_fee_structures, so an agent still has to infer which fee-related getter 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?

Strong precondition guidance: call check_business_tool_access before collecting inputs, FREE businesses are blocked regardless of feature rows, and never proceed when access is blocked. What is missing is guidance on choosing this tool over the other fee-related siblings, and the 'when not to use' is limited to the permission gate.

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