Skip to main content
Glama

create_config

Create a Portkey configuration defining request routing, caching, retry behavior, and targets.

Instructions

Create a config that defines routing, cache, retry, and targets for requests; use update_config to modify an existing one and list_config_versions for history. At least one setting is required, new configs become active immediately once referenced by a key or prompt, and the call returns the new id and 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": {
      "name": "<name>"
    },
    "name": "create_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName for the new configuration
targetsNoArray of target providers with virtual keys
cache_modeNoCache mode: 'simple' or 'semantic'
auto_cachingNoAutomatically add Anthropic prompt caching. Set false to disable
workspace_idNoWorkspace ID to create config in
cache_max_ageNoCache max age in seconds
strategy_modeNoRouting strategy: 'loadbalance' or 'fallback'
retry_attemptsNoNumber of retry attempts (1-5)
retry_on_status_codesNoHTTP status codes to retry on (e.g., [429, 500, 502, 503])

Output Schema

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.16.5
    • 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. Changed1 schema field changedv0.16.4
    • addedInput schema / properties / auto_caching
      Added value: +{
      +  "description": "Automatically add Anthropic prompt caching. Set false to disable",
      +  "type": "boolean"
      +}
  3. 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"
  4. 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"
  5. Addedv1.0.1
  6. Removed
  7. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower, and the description still adds non-obvious behavior: new configs become active immediately once referenced by a key or prompt. It also notes the call returns the new id and version_id, though that is partly redundant with the output schema, and says nothing about failure modes or permissions for workspace_id.

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?

A single front-loaded sentence with no filler; every clause carries distinct information (purpose, alternatives, constraint, activation semantics, return). It is dense and semicolon-packed, which slightly reduces scannability, but nothing is wasted.

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 9-parameter creation tool with full schema coverage, an output schema, and annotations present, the description covers purpose, alternatives, activation timing, and the minimum-setting rule. Remaining gaps (workspace scoping, target/strategy interaction) are handled adequately by the richly described schema.

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 a real constraint beyond the schema: the schema only requires 'name', while the text specifies at least one setting must be supplied. That meaning is not derivable from the structured fields and materially affects how the agent fills the optional cache/retry/targets parameters.

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 and enumerates what the resource contains (routing, cache, retry, targets), then explicitly names the sibling tools that handle modification and history. An agent can distinguish this from update_config and list_config_versions without opening any schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use update_config to modify an existing config and list_config_versions for history, which is exactly the when-to-use-this-vs-alternatives guidance the dimension asks for. The mandatory-setting constraint ('At least one setting is required') further gates correct invocation.

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