Skip to main content
Glama

update_subscription_rate_plan_charge

Update a subscription rate plan charge by modifying pricing, quantity, charge model, billing cycle, and optional tiers. Required: charge type and end date condition.

Instructions

Update a rate plan charge on a subscription. PUT /subscriptions/{subscriptionId}/rateplan-charges/{chargeId}. Required: subscriptionId, chargeId, quantity, name, chargeModel (flatFeePricing|perUnitPricing|tieredPricing|volumePricing), billCycleType, chargeTier (array: currency, price required). For price, you can pass a string dollars '41.00' or integer cents 4100 – the tool always sends cents to the API (same logic as create_invoice detail.amount). Also required: chargeType (oneTime|recurring|usage), endDateCondition (subscriptionEnd|fixedPeriod), taxable (boolean), weight. When chargeType is recurring, billingPeriodAlignment is also required. Optional: billingPeriod, billingTiming, specificBillingPeriod.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscriptionIdYesSubscription ID (required)
chargeIdYesSubscription rate plan charge ID (required)
quantityYesQuantity (required)
nameYesCharge name (required)
chargeModelYesRequired. flatFeePricing|perUnitPricing|tieredPricing|volumePricing
billCycleTypeYesRequired. chargeTriggerDay|defaultFromCustomer|specificDayOfMonth|specificDayOfWeek|specificMonthOfYear|subscriptionStartDay|subscriptionFreeTrial
chargeTierYesRequired. Array of tiers: currency (required), price (required as '41.00' (dollars) or 4100 (cents); tool always sends cents to API), optional startingUnit, endingUnit, priceFormat, tier
chargeTypeYesRequired. oneTime|recurring|usage
endDateConditionYesRequired. subscriptionEnd or fixedPeriod
taxableYesRequired. Whether the charge is taxable
weightYesRequired. Weight (integer)
billingPeriodNoday, week, month, year
billingTimingNoinAdvance, inArrears
billingPeriodAlignmentNoRequired when chargeType is recurring. alignToCharge, alignToSubscriptionStart, alignToTermStart
specificBillingPeriodNoSpecific billing period
Behavior4/5

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

With no annotations, the description carries full burden. It discloses a key behavioral trait: price conversion (dollars vs cents) and that the tool always sends cents to API. It also notes conditional requirement for billingPeriodAlignment when chargeType is recurring. However, it omits side effects or failure modes.

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 a single paragraph with front-loaded purpose and endpoint. It covers essential details without redundancy, though it could be broken into sections for readability. No wasted sentences.

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?

Given 15 parameters, no output schema, and no annotations, the description addresses critical aspects like price handling and conditional fields. It lacks details on return values, error handling, or what happens to existing charges, leaving some gaps for a complex update tool.

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 each parameter has a basic description. The tool description adds extra context for price conversion and conditional requirement, but otherwise does not significantly enhance meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Update a rate plan charge on a subscription'), specifies the HTTP method and endpoint, and includes the tool's purpose. It distinguishes itself from sibling tools like 'add_subscription_rate_plan_charge' by focusing on updates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description lists required fields but does not explicitly state when to use this tool versus alternatives like 'update_subscription' or 'add_subscription_rate_plan_charge'. It lacks explicit guidance on prerequisites or when-not-to-use, relying on the name to imply update context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rhinosaas/rebillia-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server