Skip to main content
Glama

List datasets

list_datasets
Read-onlyIdempotent

Call this to find versioned datasets by topic: AI provider incidents, MCP server liveness, SDK and tool releases, API latency and more. Returns each project's slug, title, access (public or paid), visibility, latest version and record count. query keeps the projects whose slug or title contains the word; left out, every project. Free, no key; your operator's private projects appear only with your key. Next: dataset_info with a slug for the readme and schema, read_dataset for its records. With an agent key, query_dataset runs SQL over a version.

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
queryNoa keyword: keeps projects whose slug or title contains it, up to 100 characters; left out, every project

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"substring filter on slug or title"New value: +"a keyword: keeps projects whose slug or title contains it, up to 100 characters; left out, every project"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world; the description adds behavior the annotations cannot: it is free and needs no key, and private operator projects appear only when a key is supplied. That access/auth nuance is exactly the kind of context an agent needs before calling.

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?

Purpose, return shape, parameter behavior, and next steps are front-loaded in a logical order with no filler sentences. It is dense — six clauses packed into a short block — but each one carries information an agent would otherwise have to guess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by naming every returned field. With one optional, fully documented parameter and a read-only annotation profile, nothing needed to call the tool correctly is missing.

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 'query' parameter is already fully documented, including the 100-character limit and the substring match on slug or title. The description restates the same matching rule and the default ('left out, every project') without adding syntax or format detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ('find versioned datasets') and enumerates the concrete topics covered (AI provider incidents, MCP liveness, SDK releases, API latency), which makes it clearly distinct from siblings like dataset_info or search_knowledge. It also previews exactly what is returned (slug, title, access, visibility, latest version, record count).

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

Usage Guidelines5/5

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

Explicitly routes the agent forward: 'Next: dataset_info with a slug for the readme and schema, read_dataset for its records' and 'With an agent key, query_dataset runs SQL over a version.' This names the alternatives and the conditions that select them, so no inference is required.

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.