Skip to main content
Glama
Sign In
android-sqlite-inspector

android-sqlite-inspector

by hortusys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Schema Diff

schema_diff

Compare two SQLite database schemas to identify added or removed tables and columns.

Instructions

Compare schemas of two databases. Shows added/removed tables and columns.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "database_old": "<database_old>",
      "database_new": "<database_new>"
    },
    "name": "schema_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
database_newYesNew database filename
database_oldYesOld database filename

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states that the tool 'Shows added/removed tables and columns,' which conveys the core behavior, but it does not explicitly state that it is read-only, whether it has side effects, or how results are structured beyond that high-level summary.

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 two concise sentences with no filler. The primary purpose is front-loaded, and the second sentence adds useful output scope without unnecessary verbosity.

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?

This is a simple two-parameter comparison tool with no output schema, and the description covers the essential return insight: added/removed tables and columns. It does not describe exact output formatting or error behavior, but for a tool of this complexity the description is reasonably complete.

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?

The input schema already fully describes both parameters with 'Old database filename' and 'New database filename,' giving 100% schema coverage. The description adds no additional parameter-level detail, so the baseline score of 3 is appropriate.

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 uses a specific verb and resource: 'Compare schemas of two databases.' It further specifies what the tool shows (added/removed tables and columns), making its purpose unmistakable and clearly distinct from sibling tools like list_tables or describe_table.

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 clearly communicates the scenario for using this tool: comparing two database schemas. It does not explicitly name alternatives or exclusions, but the context is clear enough that an agent would know when this tool is appropriate.

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