Skip to main content
Glama
GET-Technology-Inc

Jamf Docs MCP Server

Lookup Jamf Glossary Term

jamf_docs_glossary_lookup
Read-onlyIdempotent

Look up Jamf glossary terms and get definitions using fuzzy matching, so you can quickly understand acronyms and platform terminology.

Instructions

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

This tool searches the Jamf Platform Technical Glossary, one glossary shared by every Jamf product, and returns matching term definitions using fuzzy matching. A term of 4 characters or fewer is treated as an abbreviation and must be a whole word of the entry's name, so "DEP" does not match "zero-touch deployment". A 4-character term may be a plural, or miss a letter or swap two ("MDMs", "LDPA").

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): Accepted, but does not filter: Jamf publishes one platform-wide glossary with no product classification

  • 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, "url": string }], "tokenInfo": { "tokenCount": number, "truncated": boolean, "maxTokens": number }, "truncatedContent"?: { "omittedCount": number, "omittedItems": [{ "title": string, "estimatedTokens": number }] }, "incomplete"?: { "unfetched": [{ "term": string, "url": string }], "message": string } }

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

Examples:

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

  • "What is a configuration profile?" → term="Configuration Profile"

  • "What is Automated Device Enrollment (formerly DEP)?" → term="Automated Device Enrollment"

Errors:

  • "Glossary lookup for "" failed: ..." (isError) if learn.jamf.com could not be read (a network error, a timeout, or a server error), so the lookup cannot say whether the glossary has the term. This is not a "no match". It may be temporary: try again.

  • "Invalid option: expected one of ..." (an input validation error) if product is not a known product ID

Note: "No glossary entries found" is not an error. It means the glossary was read and no entry matches; in JSON that is "totalMatches": 0. If entries match but not even the first fits in maxTokens, the reply says how many matched and the maxTokens the first one needs: "truncatedContent" lists each entry left out and the tokens it costs. If some matching entries could not be fetched, the reply answers from the rest and says so: "incomplete" names the entries it may be missing. If the entry that would lead the answer is one of them, that is the error above instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesGlossary term to look up (e.g., "MDM", "Configuration Profile", "Automated Device Enrollment")
productNoAccepted, but does not filter: Jamf publishes one platform-wide glossary with no product classification
languageNoDocumentation language/locale (default: en-US). Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH, it-IT, pt-BR, zh-CN
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
entriesYes
truncatedYes
incompleteNo
totalMatchesYes
truncatedContentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.0.12
    • addedOutput schema / properties / truncatedContent
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "omittedCount": {
      +      "type": "number"
      +    },
      +    "omittedItems": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "estimatedTokens": {
      +            "type": "number"
      +          },
      +          "title": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "title",
      +          "estimatedTokens"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "omittedCount",
      +    "omittedItems"
      +  ],
      +  "type": "object"
      +}
  2. Changed3 schema fields changedv6.0.11
    • changedInput schema / properties / product / description
      Previous value: -"Filter by product: jamf-pro, jamf-school, jamf-connect, jamf-protect, jamf-now, jamf-safe-internet, jamf-insights, jamf-rapididentity, jamf-trust, jamf-routines, self-service-plus, jamf-app-catalog, jamf-account, jamf-security-cloud, elevate, composer, jamf-parent, jamf-teacher, jamf-setup-reset, jamf-assessment, title-editor, jamf-infrastructure-manager, jamf-adcs-connector, jamf-pki-proxy, jamf-migrate, jamf-remote-assist, jamf-cloud-distribution-service, healthcare-listener"New value: +"Accepted, but does not filter: Jamf publishes one platform-wide glossary with no product classification"
    • changedInput schema / properties / term / description
      Previous value: -"Glossary term to look up (e.g., \"MDM\", \"Configuration Profile\", \"Smart Group\")"New value: +"Glossary term to look up (e.g., \"MDM\", \"Configuration Profile\", \"Automated Device Enrollment\")"
    • addedOutput schema / properties / incomplete
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "message": {
      +      "type": "string"
      +    },
      +    "unfetched": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "term": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "term",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "unfetched",
      +    "message"
      +  ],
      +  "type": "object"
      +}
  3. Changed4 schema fields changedv5.10.1
    • changedInput schema / properties / language / description
      Previous value: -"Documentation language/locale (default: en-US). Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH"New value: +"Documentation language/locale (default: en-US). Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH, it-IT, pt-BR, zh-CN"
    • changedInput schema / properties / language / enum
      Previous value: -[
      -  "en-US",
      -  "ja-JP",
      -  "zh-TW",
      -  "de-DE",
      -  "es-ES",
      -  "fr-FR",
      -  "nl-NL",
      -  "th-TH"
      -]New value: +[
      +  "en-US",
      +  "ja-JP",
      +  "zh-TW",
      +  "de-DE",
      +  "es-ES",
      +  "fr-FR",
      +  "nl-NL",
      +  "th-TH",
      +  "it-IT",
      +  "pt-BR",
      +  "zh-CN"
      +]
    • changedInput schema / properties / product / description
      Previous value: -"Filter by product: jamf-pro, jamf-school, jamf-connect, jamf-protect, jamf-now, jamf-safe-internet, jamf-insights, jamf-rapididentity, jamf-trust, jamf-routines, self-service-plus, jamf-app-catalog"New value: +"Filter by product: jamf-pro, jamf-school, jamf-connect, jamf-protect, jamf-now, jamf-safe-internet, jamf-insights, jamf-rapididentity, jamf-trust, jamf-routines, self-service-plus, jamf-app-catalog, jamf-account, jamf-security-cloud, elevate, composer, jamf-parent, jamf-teacher, jamf-setup-reset, jamf-assessment, title-editor, jamf-infrastructure-manager, jamf-adcs-connector, jamf-pki-proxy, jamf-migrate, jamf-remote-assist, jamf-cloud-distribution-service, healthcare-listener"
    • changedInput schema / properties / product / enum
      Previous value: -[
      -  "jamf-pro",
      -  "jamf-school",
      -  "jamf-connect",
      -  "jamf-protect",
      -  "jamf-now",
      -  "jamf-safe-internet",
      -  "jamf-insights",
      -  "jamf-rapididentity",
      -  "jamf-trust",
      -  "jamf-routines",
      -  "self-service-plus",
      -  "jamf-app-catalog"
      -]New value: +[
      +  "jamf-pro",
      +  "jamf-school",
      +  "jamf-connect",
      +  "jamf-protect",
      +  "jamf-now",
      +  "jamf-safe-internet",
      +  "jamf-insights",
      +  "jamf-rapididentity",
      +  "jamf-trust",
      +  "jamf-routines",
      +  "self-service-plus",
      +  "jamf-app-catalog",
      +  "jamf-account",
      +  "jamf-security-cloud",
      +  "elevate",
      +  "composer",
      +  "jamf-parent",
      +  "jamf-teacher",
      +  "jamf-setup-reset",
      +  "jamf-assessment",
      +  "title-editor",
      +  "jamf-infrastructure-manager",
      +  "jamf-adcs-connector",
      +  "jamf-pki-proxy",
      +  "jamf-migrate",
      +  "jamf-remote-assist",
      +  "jamf-cloud-distribution-service",
      +  "healthcare-listener"
      +]
  4. Changed3 schema fields changedv4.0.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / product / description
      Previous value: -"Filter by product: jamf-pro, jamf-school, jamf-connect, jamf-protect"New value: +"Filter by product: jamf-pro, jamf-school, jamf-connect, jamf-protect, jamf-now, jamf-safe-internet, jamf-insights, jamf-rapididentity, jamf-trust, jamf-routines, self-service-plus, jamf-app-catalog"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  5. Addedv3.0.34
  6. Removedv3.0.30
  7. First observedv3.0.25

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld, yet the description adds substantial behavior beyond them: the whole-word rule for terms of 4 characters or fewer, plural/typo tolerance, English-only results even with non-English language params, and a careful distinction between a lookup failure (network/timeout, retryable, 'not a no-match') and a legitimate zero-match result.

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?

Well front-loaded with purpose, then args, returns, examples, and error/no-match semantics in a predictable order. Slight redundancy: the English-only caveat appears twice (once as a standalone note, once in the language arg), and the error section is dense, but nearly every sentence carries load-bearing information.

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?

For a 6-parameter tool with an output schema present, the description covers everything else an agent needs: fuzzy-match behavior, abbreviation rules, the no-op product parameter, truncation via truncatedContent, partial results via incomplete, and the error-vs-no-match distinction. Nothing material is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning the schema does not: product is accepted yet filters nothing, and language options are accepted but always yield English content. The fuzzy-matching and abbreviation semantics on term also go beyond the schema's example list.

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?

States a specific verb+resource (look up a term in the Jamf official glossary) and immediately scopes it: one platform-wide glossary shared by every Jamf product, with fuzzy matching. An agent can distinguish this from jamf_docs_search/get_article because the resource is explicitly the glossary, not documentation articles.

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?

Clear context for when to reach for it (definition lookup of a term) and explicit operational guidance on term length, abbreviations, and that product does not filter. It never names a sibling or says when NOT to use this versus jamf_docs_search, so routing is inferable rather than explicit.

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