Skip to main content
Glama
Sign In
Elephant MCP Server

Elephant MCP Server

by elephant-xyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List properties by class

listPropertiesByClassName

Lists non-deprecated properties for any class, giving you only the active schemas to use in data queries.

Instructions

List non-deprecated lexicon properties for one class.

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": {
      "className": "<className>"
    },
    "name": "listPropertiesByClassName"
  }
}

Input Schema

NameRequiredDescriptionDefault
classNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.13.0
    • removedInput schema / properties / className / description
      Removed value: -"The class name, case-insensitive"
  2. First observedv1.12.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does add useful selection details ('non-deprecated', 'lexicon', 'one class'), but it omits return shape, pagination, ordering, or behavior for an unknown class name.

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 description is a single, front-loaded sentence with no filler or repetition. It is efficiently structured, though arguably too terse to provide richer guidance.

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 tool, the description states the required input and the filtering rule, which is nearly enough. Missing usage contrast with siblings and return-value caveats keep it from being fully complete.

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 schema's only parameter, 'className', has no description, and the tool description partially compensates by saying the operation targets one class. However, it does not clarify the expected class-name format or whether a fully qualified name is required.

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 names a specific verb ('List') and resource ('non-deprecated lexicon properties') and scopes the operation to 'one class', so an agent can tell what the tool does. It is clear, though it does not explicitly contrast itself with sibling tools such as listAtlasProperties.

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?

No guidance is given about when to choose this tool over listAtlasProperties, getPropertySchema, or getAtlasProperty. The intended usage context must be inferred from the tool name and the phrase 'for one class.'

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

Deploy Server

Other Tools