Skip to main content
Glama
GET-Technology-Inc

Jamf Docs MCP Server

by GET-Technology-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Batch Get Jamf Documentation Articles

jamf_docs_batch_get_articles
Read-onlyIdempotent

Fetch up to 10 Jamf documentation articles in a single request to compare pages or gather information. Supports parallel retrieval with adjustable concurrency and output options.

Instructions

Retrieve multiple Jamf documentation articles in a single request.

Fetches up to 10 articles in parallel with concurrency control. Useful for comparing articles, gathering information from multiple pages, or bulk research.

Args:

  • urls (string[], required): Array of 1-10 https:// article URLs on learn.jamf.com, docs.jamf.com, concepts.jamf.com, support.jamf.com. Any other URL fails as its own per-article error

  • concurrency (number, optional): Max parallel requests 1-5 (default: 3)

  • language (string, optional): Documentation language/locale. Overrides the locale in each URL, which is used when this is omitted. No effect on concepts.jamf.com or support.jamf.com URLs

  • maxTokens (number, optional): Total token budget across all articles 100-50000 (default: 5000). Distributed evenly.

  • outputMode ('full' | 'compact'): Output detail level (default: 'full'). Use 'compact' for brief output.

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

Returns: An array of article results. Each article independently succeeds or fails. For JSON format, returns a BatchResponse object with results, summary, and tokenInfo.

Examples:

Note: Token budget is split evenly across articles. Use higher maxTokens for more articles. A note on an article (such as one about language) counts toward its share. Partial failures are reported per-article without failing the entire batch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYesArray of Jamf documentation article URLs (1-10)
languageNoDocumentation language/locale. Overrides the locale in the article URL, which is used when this is omitted. Has no effect on concepts.jamf.com or support.jamf.com URLs. Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH, it-IT, pt-BR, zh-CN
maxTokensNoTotal token budget across all articles (100-50000, default: 5000)
outputModeNoOutput detail level: "full" for detailed output or "compact" for brief outputfull
concurrencyNoMaximum parallel requests (1-5, default: 3)
responseFormatNoOutput format: "markdown" for human-readable or "json" for machine-readablemarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes
summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.0.11
    • 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, it-IT, pt-BR, zh-CN"New value: +"Documentation language/locale. Overrides the locale in the article URL, which is used when this is omitted. Has no effect on concepts.jamf.com or support.jamf.com URLs. Options: en-US, ja-JP, zh-TW, de-DE, es-ES, fr-FR, nl-NL, th-TH, it-IT, pt-BR, zh-CN"
  2. Changed2 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"
+]
  3. Changed2 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"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. First observedv3.0.25

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description reveals critical runtime behavior: concurrency control (1-5), per-article failure isolation, token budget distribution, language override semantics, and partial-failure reporting. It even notes that the language parameter has no effect on certain domains. This substantially exceeds annotation coverage.

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 organized into clear sections (Args, Returns, Examples, Note) and front-loads the core purpose. It is slightly verbose with the Args list repeating some schema details, but every sentence adds operational value. Examples are helpful but could be trimmed.

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 complex batch tool with 6 params and an output schema, the description covers all aspects an agent needs: input constraints, parameter interactions, return shape, error handling, and usage examples. It complements the output schema without duplicating field-level return details.

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?

While the schema documents all six parameters (100% coverage), the description adds meaningful semantics: how maxTokens is split evenly, that concurrency limits parallel requests, how language overrides URL locale with no effect on certain domains, and what compact mode means. It clarifies behavior that the schema alone does not convey.

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 verb 'Retrieve' and resource 'multiple Jamf documentation articles in a single request', distinguishing it from the single-article sibling by highlighting batching and parallelism. The title and opening sentence unambiguously identify this as the bulk version of get_article.

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?

The description gives concrete use cases ('comparing articles, gathering information from multiple pages, or bulk research') and includes examples. It does not explicitly name alternatives or exclusion conditions, but the batch context strongly implies when this tool is preferred over single-article fetches.

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