Skip to main content
Glama

K-12 Educational Tools & Curriculum Catalog (Math, Reading, Spanish)

List Curriculum Datasets

list_datasets
Read-onlyIdempotent

List all 9 curriculum datasets in one call, with no arguments: each entry gives the dataset id (for get_curriculum_dataset), the plain topic phrase (for get_word_list), the human-readable title, the total item count, the valid levels where the dataset has subsets (Dolch levels, CVC rimes, digraphs, Spanish syllables/words — omitted for single-level datasets), the language (en or tr-en), the shape of the items (single-word strings, or objects with tr/en/example fields — never actual words), and the source_note stating where the list came from. Use first whenever you don't know which word lists exist or which topic/level values are valid — it answers that without fetching any words. Returns the manifest only, no word lists. Requires no authentication.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
creatorYesDataset creator, always Birkan Yavuz
datasetsYesOne manifest entry per dataset: id, title, topic, count, levels (only where the dataset has subsets), language, items_sample, source_note, uri
dataset_countYesNumber of datasets listed, always 9
invocation_idYesUnique receipt id for this call

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; the description still adds real context beyond them: no arguments required, no authentication needed, and the fact that no words are fetched (a cheap discovery call). The disclosure that item shape is 'never actual words' warns the agent not to expect content. Minor gap: no note on response size or ordering of the 9 entries, though those are low-stakes for a fixed-size manifest.

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?

The lead clause is front-loaded with the core fact (9 datasets, no arguments) before the field enumeration, and every enumerated field maps to something the agent must interpret downstream. It is a long single run-on sentence, however — the field list would read faster as a short bulleted or semicolon-clause structure, and 'the plain topic phrase' wording is slightly redundant with the parenthetical that follows.

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?

Output schema exists, yet the description still pre-explains the semantic quirks an agent would otherwise have to reverse-engineer: levels omitted for single-level datasets, language values en/tr-en, and polymorphic item shape. Combined with the auth and no-fetch notes, an agent has everything needed to call this correctly and to chain into get_word_list or get_curriculum_dataset.

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, which is the baseline-4 case; the description reinforces this by stating 'with no arguments' and 'in one call,' removing any doubt that filters exist. It cannot add more because there is nothing parameterized to explain.

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 ('List all 9 curriculum datasets in one call'), plus the exact cardinality and the fields each entry carries. It also disambiguates from siblings by naming the downstream consumers of the returned values (get_curriculum_dataset, get_word_list), so an agent can distinguish this discovery tool from the fetch tools without opening a schema.

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?

Gives an explicit routing rule: 'Use first whenever you don't know which word lists exist or which topic/level values are valid.' It also states the inverse boundary — 'Returns the manifest only, no word lists' — telling the agent what this tool will not do and implicitly which sibling to call for actual words.

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.