Skip to main content
Glama
Sign In
apache-atlas-mcp

apache-atlas-mcp

by DanMeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_classifications

Retrieve all classifications and tags applied to a specific entity, such as PII or confidentiality labels, for data governance and compliance.

Instructions

Get all classifications (tags) applied to an entity.

Classifications are used for data governance — e.g., PII, Confidential, HIPAA, GDPR tags that indicate sensitivity or compliance requirements.

Args: guid: The GUID of the entity.

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": {
      "guid": "<guid>"
    },
    "name": "get_classifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
guidYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

The description implies a read-only operation by stating 'Get all classifications,' which is clear. No annotations provided, so the description carries full burden and adequately discloses the basic behavior.

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 concise (3 sentences), front-loads the purpose, and avoids redundancy.

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?

Despite lacking usage guidelines, the description covers the essential purpose and parameter adequately, and an output schema exists to explain return values, making it sufficiently complete for a simple read tool.

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?

With 0% schema coverage, the description adds meaning by explaining 'guid' as the entity's GUID, compensating for the schema's lack of description.

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 clearly states it retrieves all classifications (tags) for an entity, with specific examples like PII and HIPAA, distinguishing it from sibling tools that search or retrieve other entities.

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?

No explicit guidance on when to use this tool versus alternatives; usage is implied by the specific purpose, but no exclusions or conditions are mentioned.

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