Skip to main content
Glama
mikewegmann

baramundi MCP Server

by mikewegmann
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

list_job_instances

Retrieve paginated list of recent job executions across all devices, showing job definition, device, and execution status.

Instructions

    Listet die letzten Job-Ausführungen aller Geräte auf.

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

    Returns:
        Objekt mit 'data', 'totalItems' und 'totalPages'.
        Felder: jobDefinitionName, endpointName, state, stateDescription,
        start, lastAction, successfulExecutions, erroneousExecutions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo

Tool Definition Quality

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description must carry the burden. It discloses pagination and return format but omits authentication needs, rate limits, or read-only nature, though it reasonably implies no side effects.

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 concise and well-structured with clear Args/Returns sections. It is slightly longer due to field listing, but 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?

Given the simple tool with one parameter and no output schema, the description covers pagination, return structure, and fields adequately, though it could clarify ordering or date range.

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?

The sole parameter 'page' is explained with its default and starting index, adding meaning beyond the schema definitions despite zero schema coverage.

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 lists recent job executions for all devices, using a specific verb and resource. It distinguishes from siblings like 'get_job_instance' (single instance) and 'list_job_definitions'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description lacks context for selecting this over sibling tools like 'get_job_instance'.

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