Elephant MCP Server

List classes by data group

listClassesByDataGroup

Retrieve all lexicon classes assigned to a specified Elephant data group, enabling quick discovery of available class schemas for data modeling and integration.

Instructions

List lexicon classes in one Elephant data group.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "groupName": "<groupName>"
    },
    "name": "listClassesByDataGroup"
  }
}

Input Schema

Name	Required	Description	Default
`groupName`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.13.0Sep 22, 2026
- removedInput schema / properties / groupName / description
```
Removed value: -"The data group name, case-insensitive"
```
First observedv1.12.1Sep 5, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The word 'List' implies a read-only enumeration and the phrase 'one ... data group' communicates its scoping behavior. However, there are no annotations, so the description must fully disclose behavior itself; it does not mention pagination, error conditions, or exactness of groupName matching.

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?

The description is a single focused sentence with the verb and scope front-loaded. There is no filler or repetition of the tool name.

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

Completeness3/5

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

For a one-parameter list operation this is nearly adequate, but with no output schema and no annotations, an agent is left uncertain about what a returned 'lexicon class' looks like and what counts as a valid Elephant data group. Missing details include whether groupName must be an exact name and whether the result is a list of class names or richer class metadata.

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?

The description connects the only parameter to the concept of a data group ('one Elephant data group'), which adds some meaning beyond the bare schema property. With 0% schema description coverage, this is helpful, but it doesn't define valid group name format, allowable values, or expected examples.

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?

The description names a specific verb ('List'), a specific resource ('lexicon classes'), and a clear scope ('one Elephant data group'). This is distinct from sibling tools, which target Atlas properties, datasets, schemas, and counties rather than lexicon classes.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool instead of listPropertiesByClassName, listAtlasProperties, or other siblings. No conditions, exclusions, or alternative-selection cues are provided.

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

Deploy Server