Skip to main content
Glama

list_tables

Read-onlyIdempotent

Retrieve catalog tables with optional name filtering and pagination to find or browse tables in a workspace.

Instructions

List tables in the catalog, optionally filtered by name. Paginated.

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
limitNoPage size (1-100).
cursorNoOpaque cursor from a previous page's next_cursor.
workspaceNoNamed workspace. Omit to use the default workspace.
name_containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only the pagination trait and the optional-filter trait; it says nothing about ordering, stability of cursors across calls, or which workspace's catalog is read when the workspace parameter is omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the resource and scope; nothing is padded. The trailing 'Paginated.' fragment is efficient rather than wasteful, though it is arguably already implied by the limit and cursor parameters.

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 four-parameter, side-effect-free list tool this is close to sufficient, and the cursor parameter description covers how pages are chained. It still leaves the shape of a returned table record and the total/count semantics unstated, which matters slightly more because there is no output schema.

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 75%, with limit, cursor and workspace self-documented. The description's 'optionally filtered by name' and 'Paginated' corroborate name_contains and limit/cursor but add no syntax or matching semantics (case sensitivity, substring vs prefix) beyond what the schema provides, so the baseline 3 applies.

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 and resource ('List tables in the catalog') plus the supported filter, so the agent knows exactly what it returns. It lacks any explicit differentiation from neighbors like describe_table or sample_table, which is where a 5 would come from.

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 by the resource name and the optional name filter, but there is no statement of when to prefer this over describe_table or sample_table, and no prerequisites such as which workspace is consulted. Context is available only by inference.

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