Skip to main content
Glama

Bulk update cost rates

bulk_update_cost_rates
Destructive

Apply an organization-wide adjustment to every member's hourly COST rate, effective from a date. Supply EITHER adjustment_percentage (e.g. 5 to raise all rates by 5%, -3 to cut 3%) OR fixed_amount (add this amount to every rate, e.g. 10 raises a 100 rate to 110), not both. The organization is fixed by your context - never pass an organization id. Rate values are never echoed back.

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": {
      "effective_from": "<effective_from>"
    },
    "name": "bulk_update_cost_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixed_amountNoAmount to ADD to every member's current rate (e.g. 10 raises a 100 rate to 110), the same as the web page's Fixed Amount Increase. Provide this OR adjustment_percentage, not both.
effective_fromYesDate the adjusted rates take effect (YYYY-MM-DD) (required).
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
adjustment_percentageNoPercentage to adjust every rate by (e.g. 5 = +5%, -3 = -3%). Provide this OR fixed_amount, not both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fixed_amount / description
      Previous value: -"Set every rate to this exact amount. Provide this OR adjustment_percentage, not both."New value: +"Amount to ADD to every member's current rate (e.g. 10 raises a 100 rate to 110), the same as the web page's Fixed Amount Increase. Provide this OR adjustment_percentage, not both."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description reinforces this by specifying that the change touches every member and takes effect from a date. It adds a genuinely useful output fact — 'Rate values are never echoed back' — which matters because there is no output schema. It stops short of saying whether the change is reversible or whether history is recorded, though get_cost_rate_history implies a trail exists.

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 action and scope, then the either/or rule, then the context constraint, then the output caveat — a logical order with no filler sentences. Minor redundancy: the percentage and fixed-amount examples are duplicated verbatim from the schema descriptions.

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 destructive, no-output-schema bulk mutation, it covers date effects, mutation-mode exclusivity, identity sourcing, and the absence of echoed values. What remains unstated is whether inactive members are included and whether the change can be undone, which would be worth one more sentence.

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%, so all four parameters are already documented with equivalent examples. The description restates the percentage/fixed_amount mutual exclusion and reinforces the 'no organization id' constraint, which is real but marginal value over the structured fields.

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?

States a specific verb and resource with explicit scope: 'Apply an organization-wide adjustment to every member's hourly COST rate, effective from a date.' The word COST plus 'every member' distinguishes it from the single-user set_user_cost_rate sibling without needing to name it.

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 concrete selection rules: supply EITHER adjustment_percentage OR fixed_amount, not both, and 'never pass an organization id' because the org comes from context. It does not explicitly say when to prefer this over per-user set_user_cost_rate, so it falls short of full when/when-not guidance.

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