Skip to main content
Glama

Get resource quotas

get_resource_quotas
Read-only

Get resource quotas and current usage for namespaces.

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": {
      "cluster_id": "<cluster_id>"
    },
    "name": "get_resource_quotas"
  }
}

Input Schema

NameRequiredDescriptionDefault
namespaceNoSpecific namespace to check quotas for.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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=true, so the safety profile is covered. The description adds genuine value by noting that current usage is returned alongside the quota limits, which signals a paired limit/used shape. It stops short of describing aggregation behavior across namespaces or whether LimitRange-style constraints are included.

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?

A single, front-loaded sentence with no filler or repetition. It is arguably terse for a tool whose scope semantics are ambiguous, but nothing in it is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description is the only place to explain returns, and it does so only at a high level ('quotas and current usage'). For a two-parameter read tool that is mostly adequate, but the ambiguity around the optional namespace and the lack of routing away from provider-quota siblings leave real gaps.

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 cluster_id description even routes the agent to list_clusters, so the schema carries the parameter burden fully. The description only echoes the namespace concept ('for namespaces') without clarifying whether omitting it broadens the call to the whole cluster — a point the schema leaves implicit too.

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 pair ('Get resource quotas') plus the added payload ('current usage') and the scoping unit ('namespaces'). An agent can tell it reads quota/usage data rather than mutating it. It does not distinguish itself from close siblings like get_provider_quotas or list_limit_requests, which is the only thing keeping it from a 5.

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?

No when-to-use framing, no exclusions, and no mention of alternatives even though get_provider_quotas and list_limit_requests occupy adjacent territory. The description also leaves the reader guessing what happens when the optional namespace is omitted — all namespaces, or an error? That is exactly the decision an agent needs guidance on.

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.