Skip to main content
Glama
CodesWhat

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_usage_limits

Read-onlyIdempotent

Review cost and token usage-limit policies with current conditions, grouping, reset schedule, status, and scope. Filter by workspace, policy type, status, and page results.

Instructions

List cumulative cost or token usage-limit policies with current conditions, grouping, reset schedule, status, and scope. Filter by workspace, policy type, status, and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by budget type
statusNoFilter by active or archived status
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. Changed5 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 / type
      Added value: +{
+  "description": "Filter by budget type",
+  "enum": [
+    "cost",
+    "tokens"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / workspace_id / description
      Previous value: -"Filter usage limits by workspace ID"New value: +"Filter by workspace UUID"
  2. Addedv1.0.1
  3. Removed
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by naming what the result contains: current conditions, grouping, reset schedule, status, and scope. It does not mention pagination defaults or auth requirements, but those are less critical given the existing annotations and output schema.

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 sentences with no filler: the first front-loads the resource and expected result content, and the second compresses the filter dimensions. Every clause 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 output schema and full parameter documentation, the description covers the tool's core behavior and filter set sufficiently for an agent to call it correctly. It lacks explicit sibling disambiguation and pagination default behavior, but these are not essential for a read-only listing tool with well-specified schema.

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 five parameters are already documented with meaningful descriptions in the schema. The description merely summarizes filters ('workspace, policy type, status, and pagination') without adding new semantic detail, so the baseline of 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 uses a specific verb ('List') with a clear resource ('cumulative cost or token usage-limit policies') and enumerates the key returned aspects: current conditions, grouping, reset schedule, status, and scope. It is semantically distinct from sibling tools like list_rate_limits and list_usage_limit_entities, even without naming them.

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?

The description clearly implies a list/filter use case via the available filters, but it does not explicitly state when to prefer this over get_usage_limit or list_usage_limit_entities, nor does it describe when not to use it. A cautious agent must infer the selection from the tool name and sibling context.

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