Check the remaining GPU and TPU quota available on your Kaggle account to determine if you can run new compute tasks and avoid interruptions.
Show GPU/TPU quota remaining
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v3.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the behavioral burden. 'Show' clearly signals a read-only query with no side effects, and 'quota remaining' indicates the nature of the result. Still, it does not disclose whether authentication is needed, what units or formatting the quota is returned in, or whether quota is user-specific or project-specific.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with zero filler. Every word contributes to understanding what the tool does.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless read-only query, the description is largely sufficient: purpose and result type are clear. However, it could be more complete by noting whose quota is reported and whether the result reflects current usage or hard limits.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and the schema is empty. The description therefore needs to add no parameter-level meaning; the baseline of 4 for a parameterless tool applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Show') and a specific resource ('GPU/TPU quota remaining'), making the tool's purpose immediately clear. No sibling tool covers quota, so it is easily distinguished without opening schemas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when a user needs to check remaining GPU/TPU quota. However, it provides no explicit guidance about when to prefer this over related account/config tools, nor does it mention any preconditions or context such as account scope.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.