Skip to main content
Glama
ai-ready-warehouse

ai-ready-warehouse

by KNMDeep

list_tables

Lists tables in the ai_ready schema with descriptions and an optional name filter, helping AI assistants discover curated, documented production models.

Instructions

List the tables in the ai_ready schema: curated, documented, production models. Returns each table with its description. Optional name filter.

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
filterNoSubstring of the table name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the return shape (each table plus its description), which is genuinely useful, and "list" implies a read-only operation. It says nothing about permissions, result size, ordering, or pagination behavior for a potentially large catalog.

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, front-loaded with the resource and scope, then the return value, then the optional parameter. Nothing is redundant or padded.

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 one-optional-parameter listing tool with no output schema, the description covers what the tool returns and what the schema scope is. The remaining gaps—ordering, result volume, and how it relates to describe_table/query—are minor but real.

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 single filter parameter is already documented as a "Substring of the table name". The description only adds that the filter is optional, which is already conveyed by the zero required parameters. Baseline 3 applies since the schema does the heavy lifting.

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?

The description states a specific verb and resource ("List the tables in the ai_ready schema") and even characterizes the scope of those tables (curated, documented, production models). It never names or contrasts with the sibling tools describe_table or query, so the differentiation is left implicit rather than stated.

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 only implied: the reader can infer this is the discovery step before describe_table or query, and that the filter is optional for narrowing results. There is no explicit when-to-use or when-not-to-use guidance, and no prerequisites are mentioned.

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