Skip to main content
Glama

geezorg_list_datasets

Lists the structured datasets—dictionaries, verb paradigms, and place names—searched by the linguistic tools, including each dataset’s language and source files.

Instructions

List the structured datasets (dictionaries, verb paradigms, place names) that the geezorg tools search, with their language and source files.

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": "geezorg_list_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the whole burden; "List" reasonably implies a read-only, non-destructive operation and the description discloses the shape of what comes back (datasets, language, source files). It says nothing about cost, ordering, pagination, or whether the catalog is static or filesystem-dependent, so the behavioral picture is only partially drawn.

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?

A single sentence with the noun phrase and its examples front-loaded, followed by a short modifier about per-entry metadata. No filler, no repetition of the tool name beyond the necessary verb.

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-argument listing tool with an output schema, the description covers what is listed and what each record includes, which is the information an agent needs to decide to call it. Minor gap: no indication of catalog size or whether the result varies by environment, which could matter for planning.

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, so there is no argument semantics to explain and the baseline of 4 applies. The schema is empty and fully consistent with the description's framing of an unfiltered catalog dump.

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 ("List") and resource ("structured datasets") and enumerates the concrete contents (dictionaries, verb paradigms, place names), plus what each entry carries (language and source files). That is enough to distinguish it from geezorg_lookup, geezorg_corpus_search, and geezorg_place_names, which operate on content rather than inventorying it.

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?

Usage is only implied: an agent can infer this is a discovery/inventory step to run before searching, but the description never says when to call it, when not to, or which sibling to use instead for a given task. No prerequisites or exclusions are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.