Plori

Official

by plori-ai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Get disk usage

get_disk

Read-only

Retrieve your account's disk state: included, purchased, and used bytes, plus monthly cost. Monitor storage usage and expenses.

Instructions

Get the authenticated account's disk state (included, purchased, used bytes, and monthly cost).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`used_bytes`	Yes
`total_bytes`	Yes
`trash_bytes`	No
`usage_stale`	No	True when a mount is holding one of the account's disks but has not reported its usage within the writer-lease lifetime. used_bytes is then the last figure that mount reported, not the current one — treat it as a floor and say so rather than quoting it as the account's usage.
`warning_level`	Yes
`included_bytes`	Yes
`monthly_credits`	Yes
`purchased_bytes`	Yes
`usage_observed_at`	No	When a mount last reported the used figure. Present only while a mount is holding one of the account's disks; when none is, nothing can be changing the figure and there is no reporting clock to quote.
`storage_credits_per_gb`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.16.0Sep 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "included_bytes": {
+      "type": "integer"
+    },
+    "monthly_credits": {
+      "type": "integer"
+    },
+    "purchased_bytes": {
+      "type": "integer"
+    },
+    "storage_credits_per_gb": {
+      "type": "integer"
+    },
+    "total_bytes": {
+      "type": "integer"
+    },
+    "trash_bytes": {
+      "type": [
+        "null",
+        "integer"
+      ]
+    },
+    "usage_observed_at": {
+      "description": "When a mount last reported the used figure. Present only while a mount is holding one of the account's disks; when none is, nothing can be changing the figure and there is no reporting clock to quote.",
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "usage_stale": {
+      "description": "True when a mount is holding one of the account's disks but has not reported its usage within the writer-lease lifetime. used_bytes is then the last figure that mount reported, not the current one — treat it as a floor and say so rather than quoting it as the account's usage.",
+      "type": "boolean"
+    },
+    "used_bytes": {
+      "type": "integer"
+    },
+    "warning_level": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "included_bytes",
+    "purchased_bytes",
+    "total_bytes",
+    "used_bytes",
+    "warning_level",
+    "storage_credits_per_gb",
+    "monthly_credits"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv0.3.0Jul 26, 2026
- addedInput schema / properties
```
Added value: +{}
```
First observedv0.1.0Jul 4, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safe read-only nature is covered. The description adds useful scoping ('authenticated account's') and mentions monthly cost, but it does not disclose other behavioral details like response shape or potential delays; the output schema covers return format.

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?

A single, front-loaded sentence contains all essential information without repetition or filler. Every phrase adds meaning.

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?

For a zero-parameter, read-only tool with an output schema, the description is complete. An agent can correctly determine when and how to invoke this tool without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters, so the baseline is 4. The description adds value by naming the output fields, which is sufficient for a parameterless tool.

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 uses a specific verb ('Get') and resource ('disk state') and enumerates the exact data returned: included, purchased, used bytes, and monthly cost. This clearly distinguishes the tool from siblings like get_usage or get_credits.

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

Usage Guidelines3/5

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

The description implies use when you need the authenticated account's disk usage or cost, but it does not explicitly say when to use this tool versus alternatives such as get_usage. There is no exclusion or comparison to sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.