Skip to main content
Glama
mcp-readonly-db

mcp-readonly-db

List tables

list_tables
Read-onlyIdempotent

Lists all tables and views in a SQLite database with row counts, helping you identify available data before writing read-only SELECT queries.

Instructions

List every table and view in the database with its row count. Start here.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds that views are included and that row counts are returned, but says nothing about whether row counts are exact or estimated, how expensive they are to compute on large schemas, or how results are ordered — meaningful gaps for a discovery tool.

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, with the resource scope front-loaded and the entry-point hint last. Every clause carries information: what is returned, that views are included, and where to begin.

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 zero-parameter read-only discovery tool with rich annotations and no output schema, the description covers what an agent needs to call it correctly. The only missing piece is a caution that row counts may be expensive or approximate on large databases.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the empty object schema is self-explanatory. Baseline of 4 applies because no parameter meaning is missing.

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?

States a specific verb and resource ('List every table and view in the database') and adds the payload detail 'with its row count,' which lets an agent distinguish it from describe_table and sample_rows by scope. It stops just short of naming how it differs from those siblings explicitly.

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?

'Start here' signals this is the intended entry point for database exploration, which is useful implied guidance. However, there is no explicit when-not condition, no mention of what to do next (describe_table, sample_rows, run_query), and no stated prerequisites or cost caveats.

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