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

android-sqlite-inspector

by hortusys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Room Database Info

room_info

Shows Room schema version, identity hash, and managed entities for a specified Android SQLite database file.

Instructions

Show Room database metadata: schema version, identity hash, and managed entities.

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": "<database>"
    },
    "name": "room_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
databaseYesDatabase filename (e.g. app.db)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/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. It tells what metadata is shown, and 'Show' implies a read-only operation, but it does not explicitly state side effects, error conditions, or that no modification occurs. This is adequate but not deeply transparent.

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?

A single, front-loaded sentence conveys the tool's purpose and outputs with no wasted words. Every part contributes meaning.

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?

For a one-parameter metadata tool, the description is mostly complete: it specifies the required input and lists the expected output contents. The absence of an output schema means the return structure isn't described, which is a minor gap, but overall the tool is simple enough that this is not crippling.

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%, and the schema already documents 'database' as a filename with an example. The description adds no additional parameter semantics, so the baseline of 3 applies.

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 clearly states a specific verb ('Show') and resource ('Room database metadata') and enumerates the returned contents (schema version, identity hash, managed entities). It distinguishes itself from sibling tools like list_tables/describe_table by focusing on Room-specific metadata rather than general table structure.

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 no explicit guidance about when to use this tool versus alternatives such as list_tables/list_databases. It implies usage for retrieving Room metadata but never states contexts, exclusions, or selection criteria relative to siblings.

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