Skip to main content
Glama
jupiterbak

AYX-MCP-Wrapper

by jupiterbak

get_all_job_messages

Retrieve all messages associated with a specific job to monitor progress and troubleshoot issues.

Instructions

Get all the messages for a job

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes

Implementation Reference

  • Core handler function implementing the tool logic: checks if job exists via API, fetches job messages using jobs_api.jobs_get_job_messages, formats with pprint.pformat, handles ApiException.
    def get_all_job_messages(self, job_id: str):
        """Get all the messages for a job"""
        try:
            # check if job exists
            job = self.jobs_api.jobs_get_job_v3(job_id)
            if not job:
                return "Error: Job not found"
            
            api_response = self.jobs_api.jobs_get_job_messages(job_id)
            return pprint.pformat(api_response)
        except ApiException as e:
            return f"Error: {e}"
  • MCP tool registration: decorator @self.app.tool() registers the function as a tool, which delegates execution to the underlying tools.get_all_job_messages method.
    @self.app.tool()
    def get_all_job_messages(job_id: str):
        """Get all the messages for a job"""
        return self.tools.get_all_job_messages(job_id)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It implies a read operation ('Get') but doesn't cover aspects like pagination, rate limits, authentication requirements, error conditions, or the format/structure of returned messages. This leaves significant gaps for an agent to understand how to handle the tool effectively.

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 a single, straightforward sentence that efficiently conveys the core action without unnecessary words. It's front-loaded with the key information, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a read operation with 1 parameter) and the absence of annotations and output schema, the description is incomplete. It doesn't provide enough context about the tool's behavior, parameter usage, or expected outputs, which could hinder an agent's ability to use it correctly without additional trial or error.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter with 0% description coverage, and the tool description doesn't add any semantic details about the 'job_id' parameter. It doesn't explain what constitutes a valid job ID, where to obtain it, or any constraints, failing to compensate for the schema's lack of documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('all the messages for a job'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_job_by_id' or 'get_job_output_data', which might also retrieve job-related data, so it doesn't achieve full sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. For example, it doesn't specify if this is for retrieving message logs, status updates, or other types of messages, nor does it mention prerequisites like needing a valid job ID from another operation.

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/jupiterbak/AYX-MCP-Wrapper'

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