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

apache-atlas-mcp

by DanMeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_glossary_term

Retrieve a glossary term by its GUID to get the full term including definition, linked entities, related terms, and category assignments.

Instructions

Get a glossary term by its GUID.

Returns the full term including definition, linked entities, related terms (seeAlso), and category assignments.

Args: term_guid: The GUID of the glossary term.

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": {
      "term_guid": "<term_guid>"
    },
    "name": "get_glossary_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
term_guidYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It lists returned fields but does not mention errors, permissions, or side effects. Adequate for a simple read, but could be more explicit.

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?

Two concise sentences plus parameter definition. Front-loaded with action and return list. No waste.

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 get with one parameter and an output schema, the description covers input and return content. Lacks error handling details, but overall sufficient. Lacks sibling comparison.

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

Parameters3/5

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

Schema coverage is 0%, but description adds 'The GUID of the glossary term' to the parameter. Provides basic semantics but lacks format or example detail. Baseline adjusted upward slightly.

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 'Get a glossary term by its GUID' with a specific verb and resource, and distinguishes from siblings like 'get_glossary_terms' by indicating single-term retrieval.

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?

Usage is implied (when you have a GUID), but no explicit comparison to alternatives or exclusion criteria. Lacks guidance on when to prefer this over search or get_glossary_terms.

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