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

android-sqlite-inspector

by hortusys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Query with Pagination

query_paginated

Execute SELECT queries with pagination on Android SQLite databases, specifying limit and offset to retrieve a subset of rows along with the total row count.

Instructions

Execute a SELECT query with LIMIT/OFFSET pagination. Returns results plus total row count.

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>",
      "sql": "<sql>",
      "limit": "<limit>"
    },
    "name": "query_paginated"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlYesSQL SELECT query
limitYesMaximum rows to return
offsetNoNumber of rows to skip (default 0)
databaseYesDatabase filename (e.g. app.db)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 disclosure burden. It does add useful behavior: the LIMIT/OFFSET pagination style and the total-row-count return value. It does not state read-only semantics, how the total is computed, or behavior on invalid SQL, which are meaningful gaps given zero annotation coverage.

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 short sentences, front-loaded with the action and scoping. No wasted words — defines what it does (SELECT with pagination) and what it returns (results + total count).

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?

With no annotations and no output schema, the description covers the essential purpose and return shape but leaves gaps: how to pass dynamic values, whether the total reflects pre- or post-pagination, and what happens for non-SELECT statements. Adequate for selection, thinner for invocation edge cases.

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 baseline is 3. The description confirms the limit/offset pair maps to LIMIT/OFFSET pagination, which adds a little nuance, but it does not explain parameterization, quantifiers, or value syntax beyond the schema.

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?

Clear verb+resource: executes a SELECT query with LIMIT/OFFSET pagination, and explicitly discloses it returns results plus total row count. The pagination scoping distinguishes it from a pplain query tool.

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 by the pagination focus — an agent can infer this tool should be chosen when LIMIT/OFFSET pagination is needed. However, there is no explicit when-to-use/when-not-to-use guidance or named alternatives among siblings like query or describe_table.

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