Skip to main content
Glama

update_provider

Destructive

Update provider metadata, usage limits, rate limits, or expiration dates, and reset accumulated usage counters when quota tracking needs a fresh start.

Instructions

Update a provider's metadata, limits, or expiration. reset_usage clears accumulated usage counters immediately, so use it only when you intend to reset quota tracking. Returns the updated provider id and slug. Limit updates read the current limits and write them back, and Portkey has no conditional writes, so concurrent limit updates to the same resource can overwrite each other. Serialize them.

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": {
      "slug": "<slug>"
    },
    "name": "update_provider"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew display name for the provider
noteNoNew note or description for the provider
slugYesThe slug of the provider to update
expires_atNoNew expiration date in ISO 8601 format
reset_usageNoSet to true to reset accumulated usage metrics
credit_limitNoNew credit limit for usage
workspace_idNoWorkspace ID - required when using organization admin keys
periodic_resetNoReset period: 'monthly' or 'weekly'. If omitted, preserves the existing cadence, including custom reset days; defaults to 'monthly' when no limits exist.
alert_thresholdNoNew alert threshold percentage (0-100)
rate_limit_unitNoRate limit unit: 'rpm' (requests per minute), 'rph' (requests per hour), or 'rpd' (requests per day). Must be provided together with rate_limit_value.
rate_limit_valueNoNew rate limit value. Must be provided together with rate_limit_unit.
usage_limit_typeNoUsage limit type: 'cost' or 'tokens'. If omitted, preserves the existing type; defaults to 'cost' when no limits exist.

Output Schema

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.16.5
    • changedInput schema / properties / periodic_reset / description
      Previous value: -"Period for resetting usage limits: 'monthly' or 'weekly'. Defaults to 'monthly'."New value: +"Reset period: 'monthly' or 'weekly'. If omitted, preserves the existing cadence, including custom reset days; defaults to 'monthly' when no limits exist."
    • changedInput schema / properties / rate_limit_unit / description
      Previous value: -"Rate limit unit: 'rpm' (requests per minute), 'rph' (requests per hour), or 'rpd' (requests per day)"New value: +"Rate limit unit: 'rpm' (requests per minute), 'rph' (requests per hour), or 'rpd' (requests per day). Must be provided together with rate_limit_value."
    • changedInput schema / properties / rate_limit_value / description
      Previous value: -"New rate limit value"New value: +"New rate limit value. Must be provided together with rate_limit_unit."
    • changedInput schema / properties / usage_limit_type / description
      Previous value: -"Type of usage limit: 'cost' (monetary) or 'tokens' (token count). Defaults to 'cost'."New value: +"Usage limit type: 'cost' or 'tokens'. If omitted, preserves the existing type; defaults to 'cost' when no limits exist."
    • changedOutput schema / properties / data / description
      Previous value: -"Structured success payload when ok is true"New value: +"Success payload"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured error payload when ok is false"New value: +"Failure details"
    • changedOutput schema / properties / error / properties / details / description
      Previous value: -"Optional structured error details"New value: +"Extra error details"
    • changedOutput schema / properties / error / properties / message / description
      Previous value: -"Human-readable error message"New value: +"Error message"
    • changedOutput schema / properties / ok / description
      Previous value: -"Whether the tool call succeeded and returned structured data"New value: +"Call succeeded"
  2. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Addedv1.0.1
  4. Removed
  5. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds genuinely non-obvious behavior: limit updates are read-modify-write with no conditional writes, so concurrent updates can silently overwrite each other, and callers must serialize. It also discloses that reset_usage clears counters immediately. What's missing is any statement about what else an update can clobber (e.g., whether omitted fields are preserved).

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?

Four sentences, each front-loaded around a distinct concern: scope, side effect, return value, concurrency hazard. The return-value sentence ('Returns the updated provider id and slug') duplicates what the output schema already declares, a minor redundancy, but nothing else is padding.

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 12-parameter destructive mutation with full annotation and output-schema coverage, the description supplies the two things structured fields can't: the reset_usage side effect and the lost-update hazard. It stops short of describing preservation semantics for omitted fields or permission requirements, but the essentials for correct invocation are present.

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 the schema already documents all 12 parameters including enums and mutual-dependency notes for rate_limit_unit/value. The description adds meaning mainly for reset_usage ('clears accumulated usage counters immediately') and implies the read-back/write-back nature of limit fields, but adds nothing for name, note, expires_at, alert_threshold, or usage_limit_type. Baseline 3 is appropriate.

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 plus the field categories it touches ('metadata, limits, or expiration'), which tells an agent this is the general-purpose provider mutator. It does not address overlap with the update_rate_limit and update_usage_limit siblings, which also appear to handle limits, so an agent cannot fully rule them out from the description alone.

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?

Gives explicit conditional guidance for one parameter ('use it only when you intend to reset quota tracking') and a serialization instruction for limit updates. However, it never says when to choose this tool over update_rate_limit/update_usage_limit for limit changes, and prerequisites such as the org-admin-key case are left to the schema.

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

Deploy Server

Other Tools