Skip to main content
Glama
Sign In
feature-tracker-mcp

feature-tracker-mcp

by spe-investigator
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

db_backups

Find database backups on disk for a project, ordered newest first, to locate the latest available restore point.

Instructions

Backups on disk, newest first.

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": "db_backups"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoDirectory identifying the project and the tree. Defaults to this session's working directory, which in a git worktree is that worktree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Without annotations, the description carries the burden. It does disclose that backups are stored on disk and returned newest first, but it does not state whether the operation is side-effect-free, what a backup entry contains, or what happens when no backups exist.

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 only four words, all of which are meaningful, and the key ordering behavior is front-loaded. There is no filler or redundant restatement of the tool name.

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

Completeness3/5

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

For a low-complexity tool with one optional parameter and no output schema, this is minimally viable: it states where backups live and the sort order. However, without an output schema, it does not describe the shape of a backup entry or behavior on no backups, so an agent must infer the return format.

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

Parameters3/5

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

Schema description coverage is 100%, so the cwd parameter is already fully documented in the schema. The description adds no further parameter-level meaning beyond what is provided.

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 identifies the resource ('backups') and the key ordering behavior ('newest first'), and the plural name distinguishes it from the sibling db_backup. However, there is no explicit verb such as 'list' or 'retrieve', so the action is implied rather than stated.

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?

No guidance states when to call this over db_backup, db_restore, or stash_list. The description does not provide context, prerequisites, or alternatives; usage must be inferred from sibling names.

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

Deploy Server

Other Tools