Skip to main content
Glama
CodesWhat

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

reset_usage_limit_entity

Destructive

Reset a tracked entity's usage counter to clear its limit and immediately restore access under the specified policy.

Instructions

Reset the current usage counter for one tracked usage-limit entity. This changes enforcement immediately for that exact policy and entity, so use the entity id returned by list_usage_limit_entities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limit_idYesUsage-limit policy UUID
entity_idYesTracked entity UUID to reset

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. Changed4 schema fields changedv0.11.5
    • changedInput schema / properties / entity_id / description
      Previous value: -"Entity ID to reset usage for"New value: +"Tracked entity UUID to reset"
    • addedInput schema / properties / entity_id / minLength
      Added value: +1
    • changedInput schema / properties / limit_id / description
      Previous value: -"Usage limit policy ID"New value: +"Usage-limit policy UUID"
    • addedInput schema / properties / limit_id / minLength
      Added value: +1
  2. Addedv1.0.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds meaningful behavioral context by warning that enforcement changes immediately and that the reset applies to exactly one policy-entity pairing, which goes beyond the structured annotations.

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?

The description is two sentences with no filler. The main action is stated first, followed by a critical scoping and sourcing caveat that earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation tool with a full input schema, output schema, and clear annotations, the description sufficiently explains the operation's effect, scope, and how to get the required entity id. Nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already documents both parameters with clear descriptions and 100% coverage. The description adds extra value by specifying that entity_id should come from list_usage_limit_entities, which helps the agent retrieve the correct value.

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 and resource: 'Reset the current usage counter for one tracked usage-limit entity.' It also clarifies the scope ('that exact policy and entity'), distinguishing it from operations like deleting or updating the usage limit itself.

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 provides clear context about the immediate enforcement change and instructs the agent to use the entity id returned by list_usage_limit_entities. However, it does not explicitly state when to use this tool instead of related alternatives such as delete_usage_limit or update_usage_limit.

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