Skip to main content
Glama

List Datasets Tool

list-datasets
Read-onlyIdempotent

List datasets the current user can view, including architecture metadata. Omit project_id to include every permitted dataset in the space, plus the four system log tables: dl_trans_runs, dl_retl_runs, dl_retl_deliveries, and dl_dropped_requests.

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

Input Schema

NameRequiredDescriptionDefault
spaceNoSpace slug. Required when the token is bound to more than one space. Omit it when the token has one space.
project_idNoOptional project id. When omitted, datasets from every permitted project are returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 safety profile is covered. The description adds a non-obvious behavioral detail that the response includes four extra system log tables (dl_trans_runs, dl_retl_runs, dl_retl_deliveries, dl_dropped_requests) when project_id is omitted — an agent could easily mistake these for user datasets. Pagination/result-size behavior is still undisclosed.

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 sentences, front-loaded with the purpose and then the scoping rule plus the system-table caveat. Every sentence carries content; the enumerated table names are long but justified because they are the surprising part.

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 two-parameter, read-only, no-output-schema list tool, the description covers purpose, the token/space/project interaction at the schema level, and the anomalous inclusion of system tables. Only ordering and pagination behavior of the returned list are left unaddressed, which is minor.

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%, so both parameters are already documented, and the description's note about omitting project_id largely restates the schema text. The space parameter is never mentioned in the description, so no meaning is added beyond structured data. 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 (list) and resource (datasets) plus the scope (datasets the current user can view) and mentions architecture metadata. It does not distinguish itself from sibling get-dataset-metadata or list-dashboard-structure, so an agent still has to infer the split between listing and per-dataset retrieval.

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?

Gives one conditional rule (omit project_id for all permitted projects), which is genuine when-to-use guidance for one parameter. It says nothing about when to prefer this over get-dataset-metadata for a single dataset, nor any prerequisite such as a space selection when the token spans multiple spaces.

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