Skip to main content
Glama

List Database Tables

list_tables
Read-onlyIdempotent

Lists tables and views in a MySQL database, optionally targeting a specific database via JDBC URL. Use it to inspect schema structure and discover available data objects.

Instructions

List the tables and views in the configured MySQL database.

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
jdbc_urlNoOptional JDBC URL to target a specific database (credentials embedded in URL); uses environment default when omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.1
    • addedInput schema / properties / jdbc_url
      Added value: +{
      +  "description": "Optional JDBC URL to target a specific database (credentials embedded in URL); uses environment default when omitted",
      +  "type": "string"
      +}
  2. First observedv1.0.1

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds essentially nothing beyond that: it does not say whether system schemas are included, how views are distinguished from tables, whether results are paged, or what happens when the connection is unavailable.

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?

One sentence, front-loaded with the verb and resource, with zero filler or redundant restatement of the title. Nothing in it could be cut without losing scope information.

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?

For a one-optional-parameter, read-only listing tool with full annotation coverage, the definition is minimally adequate. However, with no output schema, the description should say something about the shape of the result (e.g., names only, schema-qualified, includes views flagged) and whether the connection target changes the result set.

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?

There is a single optional parameter at 100% schema description coverage, so the schema already fully explains jdbc_url including embedded credentials and the environment-default fallback. The description contributes no additional meaning about that parameter, making the baseline 3 appropriate.

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 ("List") and resource ("tables and views") scoped to "the configured MySQL database," which is clear enough to distinguish it from describe_table or query_database at a glance. It stops short of explicitly naming the sibling tools it is not, so it lands at 4 rather than 5.

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?

The use case (discovering what tables/views exist) is only implied by the verb; there is no explicit "use this when..." and no mention of when to prefer describe_table, list_indexes, or query_database instead. The phrase "configured MySQL database" hints at the default-connection context but does not spell out prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.