Skip to main content
Glama

Request provider quota increase

request_provider_quota_increase
Destructive

Raise a cloud-provider limit for a credential, or produce the exact request a person has to submit when the provider has no API for it. Call get_provider_quotas first: it names the dimensions and says whether the provider is automatable. Azure is the only provider Ankra can submit to (through the Microsoft.Quota API); for Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, Proxmox VE and HPE Morpheus this call still SUCCEEDS and returns status manual_action_required with a manual_action object holding the console URL, the navigation path and a ready-to-paste request_text pre-filled with the live numbers - relay that to the user rather than retrying. One call may at most double a limit (or add 16 to a small one); ask for more by repeating the call. The limit can only go up: this tool will not lower one.

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": {
      "credential_id": "<credential_id>",
      "dimension": "<dimension>",
      "new_limit": "<new_limit>"
    },
    "name": "request_provider_quota_increase"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoWhy the limit needs to grow. Carried into the provider request text and the audit record.
locationNoProvider region for a region-scoped limit. Required for Azure (for example westeurope); omit for account- or project-scoped limits.
dimensionYesLimit to raise, as reported by get_provider_quotas: an Ankra dimension name such as vcpus, servers, memory_gb, volume_gb, load_balancers or floating_ips, or for Azure an exact quota name such as cores or a SKU family like standardDSv3Family.
new_limitYesRequested new limit, in the dimension's own unit. Must be above the current limit.
credential_idYesUUID of the cloud-provider credential whose limit should be raised.
provider_namespaceNoAzure only. The ARM resource provider owning the quota. Defaults to Microsoft.Compute.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the destructive/non-idempotent annotations, it discloses the provider matrix (only Azure via Microsoft.Quota is submitted), that non-automatable providers still return success with status manual_action_required, the doubling/ +16 ceiling per call, and the one-way constraint that limits can never be lowered.

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?

Front-loaded with the action and the prerequisite, then the provider caveats, then the rate/safety constraints. Dense but every sentence carries operational value; the Azure/Hetzner list of provider names is the only mildly enumerative padding.

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?

No output schema exists, yet the description explains the success-with-manual fallback return shape (status + manual_action with console URL, navigation path, request_text) so an agent knows what comes back. Combined with the prerequisite and mutation limits, nothing essential is missing.

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%, including enum and per-field descriptions for dimension, location, provider_namespace and reason, so the baseline is 3. The description only adds indirect guidance (dimension comes from get_provider_quotas) and does not clarify parameter formats beyond 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?

The description states a specific verb+resource (raise a cloud-provider quota limit for a credential) and immediately broadens scope to the manual-request fallback, which distinguishes it from both get_provider_quotas (read) and the generic request_limit_increase sibling.

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?

It gives an explicit prerequisite ("Call get_provider_quotas first"), explains what that call tells you, defines exactly what to do when the provider is not automatable (relay manual_action rather than retrying), and states the escalation path (repeat the call for larger asks).

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.