Skip to main content
Glama

NYSgpt Data Library

List tables

list_tables
Read-only

List every table in one database with its row count. Use it to find the table that answers a question before calling describe_table.

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": {
      "database": "<database>"
    },
    "name": "list_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
databaseYesA database name from list_databases, for example govblock_awards.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that results carry row counts and that this is a cheap reconnaissance step, but it says nothing about volume limits, whether views or system tables are included, or behavior on an empty or inaccessible database. Useful, but thin beyond the annotations.

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?

Two sentences with no filler: what it returns comes first, the workflow role second. Every clause earns its place and nothing needs to be read twice.

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-parameter read-only enumeration with full schema coverage and no output schema, the definition covers purpose, return content and next step. Only the composition of the result set (views, system tables, ordering) is left implicit, which is a minor gap at this complexity.

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 coverage is 100% and the single parameter's description already points at list_databases with a concrete example, so the schema does the heavy lifting. The phrase "one database" reinforces the single-database scope, but no format or validation detail is added beyond the schema.

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?

"List every table in one database with its row count" gives a specific verb (list), a specific resource (tables), the scope (one database), and the payload (row count). It is clearly distinct from list_databases (databases, not tables), describe_table (detail, not enumeration) and query (execution, not discovery).

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

Usage Guidelines4/5

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

It states a concrete when-to-use rule — find the table that answers a question before calling describe_table — which places the tool in a precise discovery workflow. It stops short of exclusions, e.g. skipping this call when the table name is already known, so it is strong but not fully exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.