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

apache-atlas-mcp

by DanMeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_glossaries

List all business glossaries that organize terms and definitions, providing a shared vocabulary for data assets.

Instructions

List all business glossaries.

Glossaries organize business terms and definitions, providing a shared vocabulary for data assets across the organization.

Args: limit: Maximum number of glossaries to return. offset: Pagination offset.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_glossaries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must cover behavioral aspects. It explains the tool lists glossaries but lacks details on authentication, rate limits, or empty results. It minimally describes the returned data.

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 concise and includes a helpful introductory sentence about glossaries. However, it could be more structured by separating parameter details into a clearer section.

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 that an output schema exists to describe return values, the description adequately explains the tool's purpose and the meaning of glossaries. It is sufficient for a simple listing tool.

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?

The description includes 'Args' for limit and offset, but these merely restate the parameter names from the schema with no additional context like allowed ranges or behavior. Schema coverage is 0%, so the description adds minimal value.

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 'List all business glossaries,' specifying the verb and resource. It distinguishes from sibling tools like 'get_glossary' which targets a single glossary.

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?

The description implies this tool is for listing all glossaries, but does not explicitly state when to use it versus related tools like 'get_glossary' or 'search_entities'. No alternatives 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