apache-atlas-mcp

Overview Schema Source Related Servers Discussions Admin

dsl_search

Execute Atlas DSL queries to search metadata with type filters, attribute conditions, and aggregations for precise data discovery.

Instructions

Execute an Atlas DSL (Domain Specific Language) search query.

Atlas DSL supports structured queries with type filters, attribute conditions, and aggregations. Useful for complex, precise queries.

Example DSL queries:

"hive_table where name = 'customers'"
"hive_column where table.name = 'orders'"
"DataSet where owner = 'analytics_team'"

Args: query: Atlas DSL query string. limit: Maximum number of results (default: 25). offset: Pagination offset.

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": {
      "query": "<query>"
    },
    "name": "dsl_search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes
`limit`	No
`offset`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jun 11, 2026

TDQS

A4.1/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It fails to disclose whether the tool is read-only, requires authentication, or has performance implications. It only describes pagination via limit and offset.

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 and well-structured: it starts with the purpose, explains DSL briefly, gives examples, and defines parameters. Every sentence is informative and no words are wasted.

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?

Given the tool's complexity, the description covers the query syntax with examples and parameter details. An output schema exists, so return values are not needed. However, error handling or performance considerations are absent.

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

Parameters5/5

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

The input schema has 0% description coverage, but the description includes an 'Args' section that explains each parameter, their defaults, and meaning (e.g., 'query: Atlas DSL query string'). This adds significant value beyond the schema.

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 the tool's purpose: 'Execute an Atlas DSL search query.' It explains that DSL supports structured queries with type filters, attribute conditions, and aggregations, and provides example queries. This distinguishes it from sibling tools like quick_search and search_entities.

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

Usage Guidelines4/5

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

The description says the tool is 'Useful for complex, precise queries,' implying when to use it. However, it does not explicitly exclude use cases or compare with alternatives, so some guidance is missing.

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

Deploy Server