Skip to main content
Glama
GET-Technology-Inc

Jamf Docs MCP Server

Lookup Jamf Glossary Term

jamf_docs_glossary_lookup
Read-onlyIdempotent

Search Jamf's official glossary to find definitions of technical terms like MDM or Configuration Profile, with fuzzy matching support.

Instructions

Look up a term in the Jamf official glossary and get its definition.

This tool searches glossary pages across Jamf product documentation and returns matching term definitions using fuzzy matching.

Note: Glossary content is currently only available in English (en-US). Non-English language parameters are accepted but results will be in English.

Args:

  • term (string, required): Glossary term to look up (2-100 characters). Supports fuzzy matching.

  • product (string, optional): Filter by product ID (use jamf_docs_list_products to see all)

  • language (string, optional): Documentation language/locale (default: en-US). Note: glossary is English-only.

  • maxTokens (number, optional): Maximum tokens in response 100-50000 (default: 5000)

  • outputMode ('full' | 'compact'): Output detail level (default: 'full')

  • responseFormat ('markdown' | 'json'): Output format (default: 'markdown')

Returns: For JSON format: { "term": string, "totalMatches": number, "entries": [{ "term": string, "definition": string, "product": string, "url": string }], "tokenInfo": { "tokenCount": number, "truncated": boolean, "maxTokens": number } }

For Markdown format: A formatted list of glossary definitions with source links.

Examples:

  • "What is MDM?" → term="MDM"

  • "Configuration Profile in Jamf Pro" → term="Configuration Profile", product="jamf-pro"

  • "What does DEP stand for?" → term="DEP"

Errors:

  • "No matching term found" if no glossary entries match

  • "Invalid product ID" if product parameter is not recognized

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesGlossary term to look up (e.g., "MDM", "Configuration Profile", "Smart Group")
productNoFilter by product: jamf-pro, jamf-school, jamf-connect, jamf-protect
languageNoDocumentation language/locale (default: en-US). Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH
maxTokensNoMaximum tokens in response (100-50000, default: 5000)
outputModeNoOutput detail level: "full" for detailed output or "compact" for brief outputfull
responseFormatNoOutput format: "markdown" for human-readable or "json" for machine-readablemarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYes
totalMatchesYes
entriesYes
truncatedYes
Behavior5/5

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

Adds context beyond annotations, such as fuzzy matching, English-only glossary, token limits, and error messages. No contradiction with readOnlyHint, destructiveHint, idempotentHint, or openWorldHint.

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?

Well-organized with sections (note, args, returns, examples, errors), no fluff, and front-loaded essential info. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all aspects: purpose, parameters, output formats, error handling, cross-references, and examples. The output schema is detailed and referenced in the description, so no gaps remain.

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?

Schema has 100% coverage, and description enriches each parameter with constraints, defaults, and practical examples (e.g., 'term' fuzzy matching, language locale), making correct invocation straightforward.

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 action ('Look up a term') and the resource ('Jamf official glossary'), and differentiates from sibling tools like jamf_docs_search by specifying glossary-specific fuzzy matching and product filtering.

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?

Includes clear notes about language limitations and cross-reference to jamf_docs_list_products for product IDs, but lacks explicit 'when to use vs. alternatives' guidance for siblings like jamf_docs_get_article.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GET-Technology-Inc/jamf-docs-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server