Skip to main content
Glama
CodesWhat

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_usage_limits

Read-onlyIdempotent

List and filter cost or token usage-limit policies by workspace, type, status, and page, returning current conditions, grouping, reset schedule, and scope.

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

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

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. 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"
  3. Addedv1.0.1
  4. Removed
  5. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that results include current conditions, grouping, reset schedule, and scope, which is useful context beyond annotations, but says nothing about pagination limits, ordering, or authorization scope.

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?

Two tightly written sentences with the listing purpose front-loaded and the filter summary second. No filler, though the filter sentence largely restates what the schema already declares.

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 rich annotations, full schema coverage, and an output schema that carries return-value detail, the description covers the essential what and the filtering surface. Only the absence of routing guidance to the related usage-limit tools keeps it from being fully complete.

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 five parameters are documented in-schema, including both enums. The description's filter list (workspace, policy type, status, pagination) maps onto the schema without adding syntax, defaults, or semantics beyond it, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('List') and resource ('cumulative cost or token usage-limit policies') and enumerates what the records contain (conditions, grouping, reset schedule, status, scope). It is clearly distinguishable from the singular get_usage_limit and from list_rate_limits, though it never names siblings explicitly.

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

Usage Guidelines2/5

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

The description never says when to use this tool versus adjacent ones such as list_usage_limit_entities, list_rate_limits, or get_usage_limit. The filter list implies a browsing/listing scenario but provides no context, prerequisites, or exclusions.

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