Skip to main content
Glama

Lister les jeux de données

list_datasets
Read-only

List the datasets published on the portal you are called from, with optional text search. Returns id, title, row count, and last update.

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
qNoFrench keywords for full-text search (simple terms, not sentences). Examples: "élus", "DPE", "entreprises"
pageNoPage number
sizeNoPage size. The sum of the size and of the offset (page - 1) × size cannot exceed 10000.
response_formatNoconcise: id, slug, title, summary, count, updatedAt, page. detailed: every field.concise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / page / default
      Added value: +1
    • changedInput schema / properties / page / description
      Previous value: -"Page number (default 1)"New value: +"Page number"
    • addedInput schema / properties / page / minimum
      Added value: +1
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / q / description
      Previous value: -"French keywords for full-text search (simple terms, not sentences). If 0 results, try synonyms or broader terms. Examples: \"élus\", \"DPE\", \"entreprises\", \"logement social\""New value: +"French keywords for full-text search (simple terms, not sentences). Examples: \"élus\", \"DPE\", \"entreprises\""
    • addedInput schema / properties / response_format
      Added value: +{
      +  "default": "concise",
      +  "description": "concise: id, slug, title, summary, count, updatedAt, page. detailed: every field.",
      +  "enum": [
      +    "concise",
      +    "detailed"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / size / default
      Added value: +10
    • changedInput schema / properties / size / description
      Previous value: -"Page size (default 10, max 50)"New value: +"Page size. The sum of the size and of the offset (page - 1) × size cannot exceed 10000."
    • addedInput schema / properties / size / maximum
      Added value: +50
    • addedInput schema / properties / size / minimum
      Added value: +0
    • changedInput schema / properties / size / type
      Previous value: -"number"New value: +"integer"
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "count": {
      -      "description": "Number of datasets matching the search criteria",
      -      "type": "number"
      -    },
      -    "results": {
      -      "description": "An array of datasets matching the search criteria.",
      -      "items": {
      -        "additionalProperties": false,
      -        "properties": {
      -          "id": {
      -            "description": "Unique dataset ID (required for describe_dataset and search_data tools)",
      -            "type": "string"
      -          },
      -          "page": {
      -            "description": "Link to the dataset page (must be included in responses as citation source)",
      -            "type": "string"
      -          },
      -          "summary": {
      -            "description": "A summary of the dataset content",
      -            "type": "string"
      -          },
      -          "title": {
      -            "description": "Dataset title",
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "id",
      -          "title",
      -          "page"
      -        ],
      -        "type": "object"
      -      },
      -      "type": "array"
      -    }
      -  },
      -  "required": [
      -    "count",
      -    "results"
      -  ],
      -  "type": "object"
      -}New value: +null
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing portal scoping ('the portal you are called from') and the concrete return fields (id, title, row count, last update). It misses things like the 10,000 result cap and pagination behavior, but those are documented in the schema.

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, both load-bearing: the first defines scope and the search capability, the second defines the return shape. It is front-loaded with the resource and contains no redundant or filler wording.

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 simple read-only listing tool with full schema coverage and no output schema, the description covers scope, optional search, and return fields adequately. The only minor gap is pagination/result-cap behavior, which the schema already explains, so nothing critical is missing for correct invocation.

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 every parameter including q, page, size, and response_format is already documented with examples and constraints. The description only echoes the existence of an optional text search parameter and adds no syntax or format detail beyond the schema, 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?

The description states a specific verb and resource ('List the datasets published on the portal') and scopes it to the calling portal, which is meaningful context. It also enumerates the fields returned. It does not explicitly distinguish itself from siblings like search_data or describe_dataset, so it stops short of a 5.

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?

The phrase 'with optional text search' implies the tool can be used both to browse all datasets and to search by keyword, which gives some usage framing. However, there is no explicit when-to-use guidance, no statement of when to prefer another tool, and no mention of prerequisites or exclusions.

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