Plori

Official

by plori-ai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Get disk usage

get_disk

Read-only

Retrieve the authenticated Plori account's disk usage and billing details, including included, purchased, and used bytes plus monthly cost.

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
`agents`	No	The account's Agents that have a disk, largest used_bytes first: where the account's usage is and how much of each Agent's is trash.
`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.17.0Oct 1, 2026

addedOutput schema / properties / agents

Added value: +{
+  "description": "The account's Agents that have a disk, largest used_bytes first: where the account's usage is and how much of each Agent's is trash.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "agent_id": {
+        "description": "The Agent's UUID.",
+        "type": "string"
+      },
+      "agent_name": {
+        "description": "The Agent's name.",
+        "type": "string"
+      },
+      "asleep": {
+        "description": "True when the Agent has no running session, which emptying its trash requires.",
+        "type": [
+          "null",
+          "boolean"
+        ]
+      },
+      "trash_bytes": {
+        "description": "How much of used_bytes emptying this Agent's trash would free. Absent when it has not been measured.",
+        "type": [
+          "null",
+          "integer"
+        ]
+      },
+      "used_bytes": {
+        "description": "Bytes this Agent's disk holds, trash included.",
+        "type": "integer"
+      }
+    },
+    "required": [
+      "agent_id",
+      "agent_name",
+      "used_bytes"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the data is for the authenticated account and enumerates the fields returned, which is useful behavioral context, but it does not address rate limits, pagination, or other operational traits.

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?

The description is a single, well-structured sentence that front-loads the verb and resource. Every clause adds specific value by listing the disk metrics returned, with no wasted words.

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

Completeness4/5

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

For a simple, parameterless read operation with annotations and an output schema, the description is nearly complete. It states the account context and the key returned fields, though it could optionally clarify when to prefer it over related tools like get_usage.

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 tool has zero parameters, so the baseline of 4 applies. There are no parameter semantics for the description to clarify beyond the schema.

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?

The description states a specific verb and resource: 'Get the authenticated account's disk state.' It also names the exact data elements returned, which makes the purpose clear. However, it does not distinguish this tool from sibling reads such as get_usage or get_credits, so it lacks explicit sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives like get_usage or get_credits. It simply states what the tool returns, leaving context and exclusions unstated.

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