Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Get Database Info

getDatabaseInfo
Read-only

Returns the database type Uptime Kuma uses, SQLite file size, and monitor history retention days so you can verify storage and data retention settings.

Instructions

Returns which database Uptime Kuma stores its data in (sqlite, mariadb or embedded-mariadb), the SQLite file's size, and how many days of monitor history it keeps (keepDataPeriodDays). Uptime Kuma can only measure and shrink SQLite; for MariaDB the size is null.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getDatabaseInfo"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
sizeYessizeBytes in KB / MB / GB
dbTypeYessqlite, mariadb or embedded-mariadb; null if Uptime Kuma did not say
canShrinkYesWhether shrinkDatabase does anything on this database
sizeBytesYesSize of the SQLite file; null for MariaDB
keepDataPeriodDaysYesDays of heartbeats and daily statistics kept before the nightly cleanup deletes them; 0 keeps them forever. Change it with updateSettings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark this as read-only and closed-world, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: for MariaDB the size is null, and only SQLite can be measured and shrunk. It does not mention permissions or response shape, but those are either not applicable or covered by the output schema.

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?

Two sentences, front-loaded with the core return values and followed by the key SQLite/MariaDB distinction. Every sentence adds distinct value with no repeated or redundant wording.

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?

Given that an output schema exists, the description need not explain return values in full. It nevertheless covers the important edge case (null size for MariaDB) and clarifies which database backends are measurable and shrinkable, making it complete for a zero-parameter read-only informational tool.

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 takes zero parameters and the schema description coverage is 100%, so no parameter clarification is needed. The description correctly focuses on return-value semantics instead of parameter documentation.

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 states a specific verb ('Returns') and precisely enumerates the returned resources: database type (sqlite, mariadb, embedded-mariadb), SQLite file size, and keepDataPeriodDays. It is clearly distinguishable from sibling tools like shrinkDatabase, which mutates rather than reports.

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?

Usage is implied through the note that Uptime Kuma can only measure and shrink SQLite, suggesting this tool is useful before attempting to shrink. However, there is no explicit when-to-use guidance, no named alternative for shrinking, and no exclusion conditions stated.

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