Skip to main content
Glama
mikewegmann

baramundi MCP Server

by mikewegmann
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

start_job

Starts a job on an endpoint for software distribution, scanning, or scripts. Preview with dry_run=true, then set dry_run=false to execute.

Instructions

    Startet einen Job auf einem Endpunkt (Softwareverteilung, Scan, Skript etc.).

    WICHTIG: Standardmäßig ist dry_run=True — der Job wird NICHT wirklich gestartet,
    sondern nur angezeigt, was passieren würde. Zum echten Starten dry_run=False setzen.
    Immer zuerst mit dry_run=True bestätigen lassen, bevor der echte Start erfolgt.

    Workflow:
      1. search_job_definitions(query='Chrome', type='install') → job_definition_id
      2. get_device(identifier='PCSWIT1234') oder search_devices(query='PCSWIT1234') → endpoint_id
      3. start_job(job_definition_id=..., endpoint_id=..., dry_run=True)  → Vorschau
      4. start_job(job_definition_id=..., endpoint_id=..., dry_run=False) → Ausführen

    Args:
        job_definition_id:        GUID der Job-Definition (aus search_job_definitions).
        endpoint_id:              GUID des Ziel-Endpunkts (aus get_device / search_devices).
        dry_run:                  True (Standard) = nur Vorschau, kein API-Aufruf.
                                  False = Job wird wirklich gestartet.
        start_if_already_assigned: True (Standard) = Job auch starten wenn bereits zugewiesen.
                                   False = nur starten wenn noch nicht zugewiesen.

    Returns:
        Bei dry_run=True: Vorschau-Objekt mit job- und endpoint-Details.
        Bei dry_run=False: Neue Job-Instanz von der API (id, state, start, ...).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNo
endpoint_idYes
job_definition_idYes
start_if_already_assignedNo

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: default dry_run=True means no actual execution, dry_run=False triggers real execution. Also explains start_if_already_assigned parameter. No contradictions.

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-structured with sections (WICHTIG, Workflow, Args, Returns), but slightly lengthy. Front-loaded with key warning about dry_run. Each sentence adds value.

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?

Despite no output schema, description explains return values for both dry_run modes. Provides workflow context with sibling tools. Does not mention error handling or permissions, but overall comprehensive for a 4-parameter tool.

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 description coverage is 0%, but the description extensively explains all four parameters: job_definition_id and endpoint_id as GUIDs, dry_run with default and effect, and start_if_already_assigned with behavior. Adds critical meaning beyond schema.

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 tool starts a job on an endpoint (Softwareverteilung, Scan, Skript etc.) and provides a specific workflow involving sibling tools, distinguishing it from other tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly outlines when to use: after obtaining job_definition_id and endpoint_id via search_job_definitions and get_device/search_devices. Emphasizes starting with dry_run=True for preview and only then dry_run=False for execution.

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/mikewegmann/baramundi_MCP'

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