Skip to main content
Glama
CodesWhat

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_rate_limit

Update a rate limit policy's name, unit, value, or conditions by ID to adjust throttling rules after creation.

Instructions

Update a rate-limit policy's name, unit, value, or non-empty conditions by id. The public contract does not allow changing its type, target, or grouping after creation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesRate-limit policy UUID
nameNoReplacement display name
unitNoReplacement reset interval
valueNoReplacement maximum
conditionsNoReplacement conditions

Output Schema

TableJSON 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. Changed9 schema fields changedv0.11.5
    • addedInput schema / properties / conditions
      Added value: +{
+  "description": "Replacement conditions",
+  "items": {
+    "properties": {
+      "excludes": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "items": {
+              "type": "string"
+            },
+            "minItems": 1,
+            "type": "array"
+          }
+        ],
+        "description": "Values to exclude"
+      },
+      "key": {
+        "description": "Match key such as api_key, virtual_key, provider, config, prompt, model, endpoint_type, mcp_server, mcp_tool, workspace_id, or metadata.*",
+        "minLength": 1,
+        "type": "string"
+      },
+      "value": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "items": {
+              "type": "string"
+            },
+            "minItems": 1,
+            "type": "array"
+          }
+        ],
+        "description": "One value or several OR-matched values; use * for wildcard matching"
+      }
+    },
+    "required": [
+      "key",
+      "value"
+    ],
+    "type": "object"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / properties / id / description
      Previous value: -"The unique identifier of the rate limit"New value: +"Rate-limit policy UUID"
    • addedInput schema / properties / id / minLength
      Added value: +1
    • changedInput schema / properties / name / description
      Previous value: -"New name for the rate limit"New value: +"Replacement display name"
    • changedInput schema / properties / unit / description
      Previous value: -"New time unit: 'rpm' (per minute), 'rph' (per hour), or 'rpd' (per day)"New value: +"Replacement reset interval"
    • changedInput schema / properties / unit / enum
      Previous value: -[
-  "rpm",
-  "rph",
-  "rpd"
-]New value: +[
+  "rpm",
+  "rph",
+  "rpd",
+  "rpw"
+]
    • changedInput schema / properties / value / description
      Previous value: -"New maximum allowed value per unit"New value: +"Replacement maximum"
    • removedInput schema / properties / value / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / value / minimum
      Added value: +0
  2. Addedv1.0.1
  3. Removed
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish that this is not read-only and not destructive. The description adds meaningful behavioral context beyond the annotations: the public contract forbids changing type, target, or grouping after creation. It does not describe partial-update semantics or response behavior, but the annotations and output schema lower the burden.

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?

Two dense sentences with no filler: the first states the action and allowed fields, the second states the key immutability constraint. The most important information is front-loaded and every sentence earns its place.

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?

Given the annotations, full schema coverage, and presence of an output schema, the description covers the core updateable fields and the important contract restriction. A minor gap is that it does not explicitly state whether omitted fields are preserved, but the overall definition is sufficiently complete for correct invocation.

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 the schema already documents id, name, unit, value, and conditions in detail. The description's mention of 'non-empty conditions' adds little beyond the schema's minItems: 1 constraint. No additional parameter-level meaning is provided that the schema does not already convey.

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?

The description uses a specific verb ('Update') and resource ('rate-limit policy'), and lists the exact mutable fields: name, unit, value, and non-empty conditions. It also distinguishes itself from creation by stating that type, target, and grouping cannot be changed after creation, which separates it clearly from sibling tools like create_rate_limit.

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?

The description makes clear this tool updates an existing policy by id and explicitly warns that type, target, or grouping cannot be changed through this tool. However, it does not explicitly name an alternative like create_rate_limit for setting those immutable fields, so the routing guidance is strong but not fully explicit.

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