Universal Database MCP Server

Snapshot Schema

snapshot_schema

Capture a database schema snapshot for later drift detection, enabling comparison against future states to identify changes.

Instructions

Take a snapshot of the current database schema for later drift detection.

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

Input Schema

Name	Required	Description	Default
`database`	No	Database key (format: "type:name")

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.3Sep 8, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations, the description must convey side effects. 'Take a snapshot' implies some persistence or state change, but it is ambiguous whether the tool is read-only or writes a stored snapshot. There is no mention of side effects, permissions, or reversibility.

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, clear sentence with no unnecessary detail. It front-loads the action and resource, and the optional parameter is handled succinctly.

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?

Given the tool's simplicity (one optional parameter), the description is largely complete. It does not mention return values or output format, but with an output schema present, this is a minor omission. It could be slightly richer by naming the expected output type.

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

Parameters5/5

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

The only parameter 'database' is well-described with its format ('type:name') and optionality (default null). The description fully clarifies the expected input, leaving no ambiguity.

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 clearly states the action (take a snapshot) and the resource (database schema), and the phrase 'for later drift detection' distinguishes it from simply viewing the schema. However, it does not explicitly name sibling tools like schema_diff, so it misses full distinction.

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 only a vague purpose ('for later drift detection') but gives no explicit guidance on when to use this tool versus alternatives such as schema or schema_diff. It lacks prerequisites, context, or typical use cases.

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

Deploy Server