get_storage_quotaRetrieve your personal Canvas storage quota and see how much space is currently used. Read-only tool for checking remaining file storage at a glance.
Get your personal Canvas storage quota and how much of it is used. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations cover the safety profile (readOnlyHint: true). The description adds context by specifying the *type* of data being returned—not just the quota, but also the currently used amount—which enhances behavioral understanding beyond the structured hints.
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 extremely concise and effective. It uses minimal language to convey maximum information, front-loading the core functionality and immediately confirming the read-only nature.
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?
Given that it is a 0-parameter, read-only tool, the description provides all necessary context for a successful invocation. There are no vital pieces of information missing for an AI agent to correctly select and use the tool.
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?
Since the tool has no parameters and 100% schema coverage, the baseline for parameter semantics is high. The description adds zero semantics, which is appropriate for a parameter-less tool.
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 explicitly defines the function as retrieving 'personal Canvas storage quota' and 'how much of it is used.' It is highly specific to the tool's purpose and cleanly distinguishes this storage function from the hundreds of other educational/course-focused sibling tools.
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?
While it does not reference a specific competing sibling tool, it clearly defines its scope ('personal Canvas storage quota'), which serves as a clear boundary for when the agent should use it. Theadditional 'Read-only' tag reinforces appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.