Skip to main content
Glama

Get provider quotas

get_provider_quotas
Read-only

Report what a cloud-provider credential is still allowed to create: the per-dimension limits and usage of the account, project, subscription or region behind it, normalized across Hetzner, OVH, UpCloud, DigitalOcean, Scaleway, Proxmox VE, HPE Morpheus and Azure. Call this when provisioning, a node-group scale-up or a load balancer fails for a reason that could be a provider limit, or before growing a cluster. Read limit_known on every dimension before drawing a conclusion: Hetzner and Scaleway expose NO limits through any API, so their dimensions carry usage only and limits_exposed is false - that is a documented provider gap, not zero headroom and not a failed read. increase_automatable says whether Ankra can raise the limit itself (Azure only) or whether a person has to; increase_instructions says exactly how.

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>"
    },
    "name": "get_provider_quotas"
  }
}

Input Schema

NameRequiredDescriptionDefault
credential_idYesUUID of the cloud-provider credential to report on, from list_credentials or list_provider_credentials.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, but the description discloses a real behavioral trap: Hetzner and Scaleway expose no limits, so their dimensions carry usage only and limits_exposed is false — explicitly not zero headroom and not a failed read. It also explains limit_known, increase_automatable (Azure only) and increase_instructions, which is exactly the context an agent needs before acting on the result.

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?

Three sentences, each doing distinct work: purpose and scope first, then when to call, then the interpretation warning and the increase fields. Dense but front-loaded with zero filler.

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?

There is no output schema, so the description carries the return-value burden and does so for the fields that could mislead an agent (limit_known, limits_exposed, increase_automatable, increase_instructions). For a single-parameter read tool of this shape, nothing needed for correct invocation or interpretation 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% and the single credential_id parameter is fully documented in the schema, so the baseline applies. The description adds only the notion that the credential resolves to an account, project, subscription or region; it does not add format or lookup detail 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?

States a specific verb and resource ('Report what a cloud-provider credential is still allowed to create'), scopes it to per-dimension limits and usage, and enumerates the supported providers. The credential-scoped framing distinguishes it from the Kubernetes-facing get_resource_quotas sibling without naming it.

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

Usage Guidelines4/5

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

Gives concrete triggers: provisioning, a node-group scale-up or load balancer failure that could be a provider limit, or before growing a cluster. It lacks explicit exclusions and does not name request_provider_quota_increase or request_limit_increase as the follow-up tool for raising a limit, so the routing to alternatives is only implied.

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.