Skip to main content
Glama

list_data_tables

Read-onlyIdempotent

List Persistent Data Tables in the workspace (id, name, fields). Use when finding a table id for record tools; never invent a display name as the table id.

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_data_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description is not burdened with the safety profile. It nonetheless adds real context beyond them: the shape of what is returned (id, name, fields) and the constraint that table ids are opaque rather than display names. Pagination and workspace scoping are not addressed, which is the only meaningful gap.

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, no filler, and the most decision-relevant clause (what it lists and what it returns) comes first. The id caveat is placed where it will actually be read rather than buried.

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 zero-parameter read tool with no output schema, the description supplies enough: what is listed, what fields come back, and when to reach for it. Minor omissions (ordering, whether all tables are returned or paged) are low-risk for an id-lookup helper.

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 and the schema is an empty object, so there is no parameter meaning to convey. Baseline for a parameterless tool applies, and the description correctly avoids inventing inputs it does not have.

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 Persistent Data Tables') and even enumerates the returned fields (id, name, fields), which lets an agent distinguish this from get_data_table (single table) and list_data_table_records (rows). It stops short of naming a sibling as an explicit contrast point, so it is clear but not maximally differentiated.

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?

Gives an explicit triggering condition — 'Use when finding a table id for record tools' — which tells the agent exactly which task selects this tool over the record-level siblings. It adds a valuable failure-mode warning ('never invent a display name as the table id') but does not state when not to use it or name an alternative for other lookups.

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.

Resources