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

apache-atlas-mcp

by DanMeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_glossary

Retrieve a glossary, its terms, and categories by providing the glossary GUID.

Instructions

Get a glossary by its GUID, including its terms and categories.

Args: glossary_guid: The GUID of the glossary.

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": {
      "glossary_guid": "<glossary_guid>"
    },
    "name": "get_glossary"
  }
}

Input Schema

NameRequiredDescriptionDefault
glossary_guidYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

No annotations provided. Description adds that it includes terms and categories, but lacks details on pagination, depth, or permissions. Output schema exists for return format.

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?

Very concise: two sentences, includes args, no wasted words. Front-loaded with purpose.

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?

For a simple retrieval tool with one parameter and an output schema, the description is sufficient. Tells what is returned (terms and categories). Siblings are many but no additional context needed.

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?

Schema description coverage is 0%, but the description explains that 'glossary_guid' is a GUID, adding meaning beyond the bare schema type.

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?

Description clearly states verb 'Get', resource 'glossary by its GUID', and includes 'terms and categories'. Distinguishes from sibling tools like 'list_glossaries' and 'get_glossary_term'.

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?

Implicitly indicates use when a specific glossary GUID is known and full details are needed, but does not explicitly compare to alternatives or state when not to use.

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