Skip to main content
Glama
ni-c

rustpad-mcp

by ni-c
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

Server statistics

get_stats
Read-onlyIdempotent

Retrieve current Rustpad server statistics: start time, documents held in memory, and documents persisted in the database.

Instructions

Reads the Rustpad server statistics: start time, number of documents currently held in memory, and the number persisted in the database (0 when the instance runs without persistence).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_timeYesUnix seconds.
database_sizeYesPersisted pads; 0 on an instance without persistence.
num_documentsYesHeld in memory right now.
start_time_isoYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "database_size": {
+      "description": "Persisted pads; 0 on an instance without persistence.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "num_documents": {
+      "description": "Held in memory right now.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "start_time": {
+      "description": "Unix seconds.",
+      "type": "number"
+    },
+    "start_time_iso": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "start_time",
+    "start_time_iso",
+    "num_documents",
+    "database_size"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior; the description adds concrete detail about what is returned, including the special case of 0 for persistence when not enabled. This goes beyond the annotations without contradicting them.

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, tight sentence with no redundant phrasing. Every clause adds useful information: the action, the subject, and the exact statistics returned.

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?

The description provides enough context for an agent to know the output contents and the special persistence case. It does not describe formatting or error conditions, but for a parameterless read-only stats tool this is sufficient and not a significant gap.

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?

There are zero parameters and the schema coverage is trivially complete, so the description needs no parameter documentation. The baseline score of 4 applies because there is nothing missing.

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?

Description opens with the specific verb 'Reads' and names the exact resource, 'Rustpad server statistics'. It enumerates the returned metrics (start time, in-memory document count, persisted document count), leaving no ambiguity about the tool's function.

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

Usage Guidelines4/5

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

The description makes clear this is a read-only monitoring call with no parameters, so an agent can infer when to invoke it for server status. It does not explicitly contrast with sibling document tools, but none of them overlap with server-level statistics, so the use case is unambiguous.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ni-c/rustpad-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server