Elephant MCP Server

Get property schema

getPropertySchema

Retrieve the lexicon schema for a specific class property, defining its data type, constraints, and allowed values.

Instructions

Return the lexicon schema for one class property.

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>",
      "propertyName": "<propertyName>"
    },
    "name": "getPropertySchema"
  }
}

Input Schema

Name	Required	Description	Default
`className`	Yes
`propertyName`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.13.0Sep 22, 2026
- removedInput schema / properties / className / description
```
Removed value: -"Class name, case-insensitive"
```
- removedInput schema / properties / propertyName / description
```
Removed value: -"Property name, case-insensitive"
```
First observedv1.12.1Sep 5, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description carries the disclosure burden. 'Return' signals a non-mutating lookup, which is a useful behavioral trait, but the description does not mention output shape, error behavior, permissions, or side-effect guarantees, so transparency is only minimal.

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?

One short sentence with no filler. The verb and resource are front-loaded, and every word contributes to the core meaning.

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

Completeness2/5

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

For a tool with no output schema, no annotations, and no usage guidance, this description is thin. An agent can infer the basic call, but it has no sense of the returned schema's structure or how this tool differs from nearby siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not explain className or propertyName beyond their implied roles in 'one class property.' The parameter names are self-evident, but no accepted values, formatting, or relationship between the two parameters is provided.

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 uses a specific verb and resource: 'Return the lexicon schema for one class property.' It clearly identifies the target object, though it doesn't explicitly differentiate from siblings like getAtlasProperty or getAtlasSchema.

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 about when to choose this tool over the sibling tools, no stated exclusions, and no mention of prerequisites. The only hint is the phrase 'one class property,' which implies a targeted lookup but falls short of explicit usage direction.

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

Deploy Server