Skip to main content
Glama
Sign In
Qora

Qora

by suveshmoza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List tables

list_tables
Read-only

Discover available database tables and views before writing queries. Optionally filter by schema to find relevant data sources.

Instructions

List tables and views the agent can query. Optionally filter by schema. Always call this (or describe_table) before writing a query against an unfamiliar table.

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
schemaNoOptional schema name. If omitted, lists tables across all non-system schemas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so no further safety disclosure is needed. The description adds a behavioral scoping detail – it only lists tables and views the agent can query – which is valuable context. It does not mention return fields, but for a read-only listing tool this is a minor omission.

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?

Three short sentences with no filler: purpose, optional parameter, and usage guidance. Each sentence serves a distinct role and information is front-loaded, making it easy for an agent to parse quickly.

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 simple listing tool with one optional parameter and no output schema, the description covers when to use it and its scope. It does not describe the return fields (e.g., table name, schema, type), but given the tool's simplicity and read-only annotation, the gap is acceptable.

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 parameter is fully documented in the schema. The description only repeats 'Optionally filter by schema' without adding format or default behavior beyond what the schema states. Baseline 3 applies.

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?

States a specific verb and resource: 'List tables and views the agent can query.' The phrase 'the agent can query' clarifies scope, and it is clearly distinct from sibling list_schemas (lists schemas) and describe_table (describes one table).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs when to call: 'Always call this (or describe_table) before writing a query against an unfamiliar table.' This provides a clear usage rule and names the alternative tool, leaving no ambiguity about when to invoke it.

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