baramundi MCP Server

list_job_definitions

List job definitions page by page, displaying 20 results per page, to browse all available job definitions.

Instructions

    Listet alle Job-Definitionen seitenweise auf (20 pro Seite).
    Für gezielte Suche besser search_job_definitions verwenden.

    Args:
        page: Seitennummer ab 0 (Standard: 0).

    Returns:
        Objekt mit 'data', 'totalItems' und 'totalPages'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_job_definitions"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 8, 2026

TDQS

A4.8/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses pagination behavior (20 per page, page number parameter) and return structure (object with 'data', 'totalItems', 'totalPages'). However, it does not explicitly state that the tool is read-only or safe, though that is implied by its listing nature.

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?

The description is very concise: two sentences plus structured Args/Returns. The first sentence immediately states the purpose, and every part adds value. No redundant or vague language.

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?

Given the low complexity (1 parameter, no output schema), the description provides complete context: it explains pagination, the parameter, and the return format. The tool's purpose is fully covered for an agent to invoke it correctly.

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?

The schema has only one parameter 'page' with a default of 0. The description adds meaning: 'Seitennummer ab 0 (Standard: 0)' (Page number starting from 0, default: 0). Since schema description coverage is 0%, the description fully compensates by clarifying the parameter's semantics.

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 'Listet alle Job-Definitionen seitenweise auf (20 pro Seite)' (Lists all job definitions page by page). It uses a specific verb ('list') and resource ('job definitions'), and distinguishes from the sibling tool 'search_job_definitions' by noting that for targeted search, the search tool should be used.

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?

The description explicitly provides usage guidance: 'Für gezielte Suche besser search_job_definitions verwenden' (For targeted search, better use search_job_definitions). This tells the agent when not to use this tool and suggests an alternative, making the decision clear.

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

Deploy Server