Skip to main content
Glama

Request limit increase

request_limit_increase
Destructive

Submit an organisation limit-increase request for review by the Ankra team: the playground memory budget (8 GB by default), the free monthly AI allowance, or the image registry storage limit (registry_storage, per registry project). The request carries a justification, one request per kind may be pending at a time, the new value must be above the current limit, and the organisation is notified when it is decided. Requires billing permissions. Use this when create_playground or resize_playground refuses for budget headroom, when the user asks for a bigger AI allowance, or when the registry is full and tightening retention (set_registry_retention) is not enough - read the current limit with get_registry_storage first. Do not retry the refused order or push.

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": {
      "kind": "<kind>",
      "justification": "<justification>"
    },
    "name": "request_limit_increase"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhich limit to raise.
requested_gbNoRequested playground memory budget in GB. Required for kind playground_memory.
justificationYesWhy the limit needs to grow. Reviewed by a person - say what will run in the extra room.
requested_storage_gibNoRequested registry storage limit in GiB per registry project, above the current limit (get_registry_storage shows it). Required for kind registry_storage.
requested_usd_per_monthNoRequested monthly AI allowance in USD. Required for kind ai_tokens.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the one-pending-request-per-kind constraint, the validation rule that the new value must exceed the current limit, the human review and organisation notification, and the billing-permission requirement. It does not explain what a successful submission returns (e.g. a request id usable with list_limit_requests) or how the 'destructive' characteristic flagged in annotations manifests for a review request, which keeps this below a 5.

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?

Purpose and the three limit kinds are front-loaded, and every clause carries operational content. The single dense paragraph packs constraints, prerequisites, and escalation paths together, making it slightly harder to scan than a short bulleted structure would be.

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?

For a five-parameter mutation tool with no output schema this covers prerequisites, per-kind validation, concurrency limits, and approval flow, which is nearly everything an agent needs to decide and call it. The main remaining gap is the return value and how to follow up on a submitted request.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: the 8 GB default for playground memory, that registry_storage is per registry project and must be above the current value, and that the justification is read by a person ('say what will run in the extra room'). It still doesn't disambiguate the kind-specific required parameters in prose, leaving that to the schema.

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 ('Submit an organisation limit-increase request for review') and immediately enumerates the three limit kinds it covers (playground memory budget, AI allowance, registry storage), which separates it from sibling request tools like request_provider_quota_increase and request_personal_ai_key.

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

Usage Guidelines5/5

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

Gives explicit trigger conditions ('when create_playground or resize_playground refuses for budget headroom', 'user asks for a bigger AI allowance', 'registry is full and tightening retention is not enough'), names the alternative to try in that last case (set_registry_retention), points to get_registry_storage for the prerequisite read, and adds a negative instruction ('Do not retry the refused order or push').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.