Skip to main content
Glama
QueryPilot MCP

QueryPilot MCP

list_tables

Read-onlyIdempotent

Lists all queryable tables and their source files so you can identify available data before writing read-only SELECT queries.

Instructions

List every table you can query, with the file it came from.

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds that the set is permission-scoped ("you can query") and that each row carries provenance ("the file it came from"), but it says nothing about ordering, completeness, or cost of the enumeration.

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 with the scope constraint first and the result-content hint second. No filler, no restatement of the name, nothing that could be cut.

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?

With zero parameters, a full annotation set, and an output schema that documents the return shape, the description only needs to establish scope and content. It does both briefly; the only remaining gap is guidance on what to call next, which is a usability nicety rather than a correctness requirement.

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 the baseline is 4 and there is no parameter meaning left to convey. The schema is fully covered and the description introduces no conflicting parameter-like concepts.

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?

Specific verb ("list") plus resource ("tables") plus a scope qualifier ("every table you can query") and a note on result content ("with the file it came from"). It distinguishes itself implicitly from describe_table by being a bulk enumeration rather than a single-table lookup, but it never names that sibling.

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: a zero-parameter enumeration reads naturally as a first-step discovery call before describe_table or run_query. However, there is no explicit "use this when..." statement, no exclusion of alternatives, and no mention of ordering or follow-up steps.

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