Skip to main content
Glama

list_usage_limits

Read-onlyIdempotent

Query cumulative cost or token usage-limit policies to review conditions, grouping, reset schedules, status, and scope; filter by workspace, policy type, or status and paginate 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_usage_limits"
  }
}

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
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. 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"
  4. Addedv1.0.1
  5. Removed
  6. 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, idempotentHint, destructiveHint=false and openWorldHint=true, so safety and repeatability are covered structurally. The description adds that results are 'cumulative' policies with reset schedules, which hints at the data model, but says nothing about ordering, auth scope, or truncation beyond the schema's page fields.

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 sentences, front-loaded with the verb and resource, with the field enumeration and filtering clause following. The list of returned attributes is somewhat padded given an output schema exists, but nothing is wasted or buried.

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 a full-coverage input schema, an output schema, and rich annotations, the description needs only to name the resource and scope, which it does. The remaining gap is competing-sibling disambiguation, which is a guidance issue rather than a completeness one.

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%, including enums for type and status, so the schema carries the parameter meaning. The description's filter summary ('workspace, policy type, status, and pagination') adds no syntax or semantics beyond the schema — 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 and resource: 'List ... usage-limit policies', and enumerates what each record carries (current conditions, grouping, reset schedule, status, scope). An agent can tell this apart from get_usage_limit or create_usage_limit, though it does not distinguish itself from close siblings like list_rate_limits or list_usage_limit_entities.

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 only usage content is 'Filter by workspace, policy type, status, and pagination', which just restates the schema. There is no statement of when to choose this tool over list_rate_limits or list_usage_limit_entities, and no exclusions or prerequisites, despite a very crowded sibling namespace.

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