baramundi MCP Server

list_devices

Retrieve a paginated list of devices by type (Windows, Mac, Linux) for overviews. Specify page number and limit per page to navigate through device inventory.

Instructions

    Gibt eine einzelne Seite der Geräteliste zurück — NUR für seitenweise Übersichten.
    NICHT für Suchen verwenden! Für Suchen nach Benutzer, Name, IP oder Gruppe
    stattdessen search_devices(query=...) nutzen — ein einziger Call, alle Geräte.

    Args:
        type: Gerätetyp — 'windows' (Standard), 'mac' oder 'linux'.
        limit: Anzahl Geräte pro Seite (Standard: 50, Max: 100).
        page: Seitennummer, beginnend bei 0 (Standard: 0).

    Returns:
        Objekt mit 'data' (Geräteliste), 'totalItems', 'totalPages' und 'currentPage'.

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_devices"
  }
}

Input Schema

Name	Required	Default
`page`	No
`type`	No	windows
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 8, 2026

TDQS

A4.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It mentions returning a single page and the return format, but does not disclose read-only nature, authentication, or other behavioral traits beyond basic pagination.

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 concise, front-loaded with a clear purpose and warning, then structured with Args and Returns sections. Every sentence adds value without waste.

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?

Given no annotations, no output schema, and 0% schema coverage, the description provides sufficient context: it explains the tool's purpose, parameters, return structure, and contrasts with a sibling. Missing an explicit statement of read-only behavior, but overall adequate.

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 0%, but the description adds meaning for all three parameters: type with examples, limit with default and max, page with starting value. Return fields are listed, compensating for the schema gap.

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 returns a single page of the device list for paginated overviews, using a specific verb and resource, and distinguishes from the sibling search_devices tool.

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 directs when to use (paginated overviews) and when not to (searches), and provides the exact alternative search_devices with arguments.

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

Deploy Server