Skip to main content
Glama

reset_usage_limit_entity

Destructive

Reset the current usage counter for a tracked usage-limit entity, immediately updating enforcement for that policy and entity. Provide the limit ID and entity ID.

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit_id": "<limit_id>",
      "entity_id": "<entity_id>"
    },
    "name": "reset_usage_limit_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
limit_idYesUsage-limit policy UUID
entity_idYesTracked entity UUID to reset

Output Schema

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.16.5
    • changedOutput schema / properties / data / description
      Previous value: -"Structured success payload when ok is true"New value: +"Success payload"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured error payload when ok is false"New value: +"Failure details"
    • changedOutput schema / properties / error / properties / details / description
      Previous value: -"Optional structured error details"New value: +"Extra error details"
    • changedOutput schema / properties / error / properties / message / description
      Previous value: -"Human-readable error message"New value: +"Error message"
    • changedOutput schema / properties / ok / description
      Previous value: -"Whether the tool call succeeded and returned structured data"New value: +"Call succeeded"
  2. 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"
  3. 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
  4. Addedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds real context beyond that: the change takes effect immediately on enforcement and is narrowly scoped to one policy/entity pair. It stops short of saying whether the reset is reversible or what happens to historical counter data.

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 tight sentences: the action and its immediate-effect scope come first, the id-provenance hint second. No filler, nothing redundant with the name or title.

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?

An output schema exists and annotations cover the safety profile, so the description does not need to explain return values. For a two-parameter mutation it covers action, scope, immediacy, and id provenance; only reversibility/history semantics are unaddressed.

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 coverage is 100%, so both UUID parameters are already documented in the schema. The description reinforces where entity_id comes from (list_usage_limit_entities) but adds no format or constraint detail for limit_id beyond calling it 'that exact policy'. 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?

States a specific verb and resource: reset the current usage counter for one tracked usage-limit entity. The scope is narrowed to 'that exact policy and entity', which separates it from policy-level siblings like update_usage_limit or delete_usage_limit.

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?

Provides one useful operational guideline — obtain the entity id from list_usage_limit_entities — but gives no when-to-use versus when-not-to-use guidance, no mention of update_usage_limit as the alternative for adjusting rather than resetting, and no preconditions such as required permissions.

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