Skip to main content
Glama
CodesWhat

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_config

Creates a Portkey configuration that defines request routing, caching, retries, and targets. Use it to establish a new config and receive its id and version_id.

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.

Input Schema

NameRequiredDescriptionDefault
nameYesName for the new configuration
targetsNoArray of target providers with virtual keys
cache_modeNoCache mode: 'simple' or 'semantic'
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
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.2/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), and the description adds genuinely new behavior: a minimum-settings constraint, that configs activate immediately once referenced by a key or prompt, and the returned id/version_id. It stops short of covering permissions or duplicate-name behavior.

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?

A single dense sentence that front-loads purpose, then alternatives, then constraints and return value. No filler, and each clause carries distinct information.

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?

With an output schema present and 100% param coverage, the description needs only to frame purpose and routing, which it does, plus activation semantics. Missing only minor edges such as name-uniqueness and workspace defaulting.

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 all eight parameters are already documented including enums and bounds. The description only loosely groups them ('routing, cache, retry, targets') and adds the 'at least one setting is required' constraint, which is a modest value-add over 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?

States a specific verb (Create) and resource (config) plus the domains it governs: routing, cache, retry, and targets. It explicitly names the sibling tools it is not (update_config, list_config_versions), so an agent can distinguish it without opening the schema.

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?

Explicitly routes the agent to update_config for modification and list_config_versions for history, which is the main ambiguity for a create_* tool. It does not state hard preconditions (e.g., whether name must be unique or a workspace must exist), so it falls short of a full when/when-not treatment.

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