Skip to main content
Glama

update_config

Update a Portkey config in place via its slug, editing routing, cache, retry, name, or status fields. Each call creates a new recoverable version and applies changes immediately.

Instructions

Update a config by slug; every call creates a new config version rather than overwriting, so earlier versions stay recoverable via list_config_versions. Only provided fields change: name, status, and all routing/cache/retry settings (cache_mode, cache_max_age, retry_attempts, retry_on_status_codes, strategy_mode, targets) are editable, while the slug stays fixed. Changes apply immediately to every API key and prompt referencing the config. Returns the update acknowledgement and new version_id.

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_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew name for the configuration
slugYesConfiguration slug to update
statusNoConfiguration status
targetsNoArray of target providers
cache_modeNoCache mode: 'simple' or 'semantic'
cache_max_ageNoCache max age in seconds
strategy_modeNoRouting strategy
retry_attemptsNoNumber of retry attempts (1-5)
retry_on_status_codesNoHTTP status codes to retry on

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool call succeeded and returned structured data
dataNoStructured success payload when ok is true
errorNoStructured error payload when ok is false

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Changed2 schema fields changed
    • addedInput schema / properties / targets / items / properties / provider / description
      Added value: +"Provider slug to route requests to"
    • addedInput schema / properties / targets / items / properties / virtual_key / description
      Added value: +"Virtual key slug to use for this routing target"
  3. Addedv1.0.1
  4. Removed
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

Goes well beyond the annotations by explaining why the call is non-idempotent (a new config version is created each time, older versions remain recoverable), and it discloses blast radius: 'Changes apply immediately to every API key and prompt referencing the config.' That reach disclosure is exactly the extra context annotations cannot carry. It stops short of stating permission/auth requirements or failure modes, so a 4 rather than 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four dense sentences, front-loaded with the versioning behavior before the field list and side effects. No sentence is filler; the return-value clause is the only candidate for trimming given the output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter mutation with wide downstream impact, it covers versioning, immutability of slug, partial-update behavior, propagation to referencing resources, and recovery via list_config_versions. With both annotations and an output schema present, nothing an agent needs to invoke this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real semantic value: it enumerates the editable field groups and states that the slug is immutable and untouched fields are preserved. That partial-update contract is not derivable from the schema alone.

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 a config by slug') and clarifies the semantics versus a naive update by noting each call creates a new version. It does not explicitly contrast with create_config or get_config, but the scope is unmistakable.

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?

Usage is implied rather than stated: 'Only provided fields change' signals partial-update semantics, and list_config_versions is named as a recovery path, not as an alternative for editing. There is no explicit when-to-use/when-not-to-use or prerequisite guidance.

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