Skip to main content
Glama
CodesWhat

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_rate_limits

Read-onlyIdempotent

Retrieve rate-limit policies and filter them by counter type, reset interval, status, target, workspace, or page to inspect current or archived conditions before making changes.

Instructions

List rate-limit policies with their current condition, grouping, rate unit, target, status, and scope. Filter before retrieving or changing one policy, especially when archived policies should be included.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by counter type
unitNoFilter by reset interval
statusNoFilter by active or archived status
targetNoFilter by LLM or MCP-tool target
page_sizeNoNumber of policies to return per page
current_pageNoZero-based page number
workspace_idNoFilter by workspace UUID

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. Changed7 schema fields changedv0.11.5
    • addedInput schema / properties / current_page
      Added value: +{
+  "description": "Zero-based page number",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / page_size
      Added value: +{
+  "description": "Number of policies to return per page",
+  "exclusiveMinimum": 0,
+  "maximum": 100,
+  "type": "integer"
+}
    • addedInput schema / properties / status
      Added value: +{
+  "description": "Filter by active or archived status",
+  "enum": [
+    "active",
+    "archived"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / target
      Added value: +{
+  "description": "Filter by LLM or MCP-tool target",
+  "enum": [
+    "llm",
+    "mcp_tools"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Filter by counter type",
+  "enum": [
+    "requests",
+    "tokens"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / unit
      Added value: +{
+  "description": "Filter by reset interval",
+  "enum": [
+    "rpm",
+    "rph",
+    "rpd",
+    "rpw"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / workspace_id / description
      Previous value: -"Filter rate limits by workspace ID"New value: +"Filter by workspace UUID"
  2. Addedv1.0.1
  3. Removed
  4. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful context about the fields returned and the archived-policy nuance, but it does not disclose deeper behavior such as pagination defaults or whether archived policies are excluded by default. This is acceptable given strong annotations, but not a standout contribution.

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 compact sentences with no filler. The action and result fields are front-loaded, and the usage guidance follows naturally without redundancy.

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?

Seven optional parameters are fully described in the schema, and an output schema exists, so the description does not need to detail return values. It provides enough selection context for an agent to know when to call it. The archived-policy hint is slightly ambiguous about default behavior, but overall it is complete enough.

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%, and all parameters have their own descriptions. The tool description reinforces the filtering idea and references status/type concepts, but it does not add meaning beyond the schema. A baseline 3 is appropriate.

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 states a specific verb ('List') and resource ('rate-limit policies') and enumerates the fields returned (condition, grouping, rate unit, target, status, scope). It also differentiates from the sibling get_rate_limit by positioning itself as the list/filter operation used before retrieving or changing a single policy.

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 phrase 'Filter before retrieving or changing one policy' clearly indicates this tool is the discovery/filtering step before get/update/delete operations. It also calls out a concrete condition ('especially when archived policies should be included'), giving the agent actionable context, though it does not explicitly name the alternative sibling.

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