Skip to main content
Glama
Sign In
readonly-db-mcp

readonly-db-mcp

by mir-shakir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

table_stats

Get approximate table size including row estimates, data and index bytes, engine, and timestamps.

Instructions

Approximate size of a table: row estimate, data/index bytes, engine, timestamps.

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": {
      "table": "<table>"
    },
    "name": "table_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYes
schemaNo
connectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Description mentions 'approximate' indicating inexactness, but with no annotations, it fails to disclose other behavioral traits like performance, required permissions, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise and front-loaded with key output info, but lacks depth and structure for a multi-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 3 parameters with zero schema coverage, no output schema, and no annotations, the description is insufficient for an agent to correctly invoke the tool. Parameter guidance and return value details are missing.

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

Parameters1/5

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

Schema has 0% coverage (no descriptions), and the tool description does not explain the meaning or format of any parameters (table, schema, connection), leaving the agent without necessary context.

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?

Description clearly states the tool provides approximate table size including row estimate, data/index bytes, engine, and timestamps. It implicitly differentiates from siblings like describe_table by focusing on size metrics, though not explicitly.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it's for size estimates but does not address when not to use it or mention sibling tools.

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