Skip to main content
Glama
Moenamatics

Opus MCP Server

by Moenamatics

get_job_results

Retrieve results from completed job executions in the Opus workflow automation platform. Provide a job execution ID to access output data when the job status is COMPLETED.

Instructions

Get the results of a completed job execution. Only works when job status is COMPLETED

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobExecutionIdYesThe job execution ID to retrieve results for

Implementation Reference

  • The main handler function for the 'get_job_results' tool. It extracts the jobExecutionId from arguments, makes a GET request to `/job/${jobExecutionId}/results` using the axios instance, and returns the response data as formatted JSON text content.
    private async getJobResults(args: any) {
      const { jobExecutionId } = args;
      const response = await this.axiosInstance.get(
        `/job/${jobExecutionId}/results`
      );
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • The tool definition in the list of tools returned by getTools(), including the name, description, and input schema requiring 'jobExecutionId'.
    {
      name: "get_job_results",
      description:
        "Get the results of a completed job execution. Only works when job status is COMPLETED",
      inputSchema: {
        type: "object",
        properties: {
          jobExecutionId: {
            type: "string",
            description: "The job execution ID to retrieve results for",
          },
        },
        required: ["jobExecutionId"],
      },
    },
  • src/index.ts:89-92 (registration)
    The switch case in the CallToolRequestSchema handler that routes calls to 'get_job_results' to the getJobResults method.
      return await this.getJobStatus(args);
    case "get_job_results":
      return await this.getJobResults(args);
    case "get_job_audit_log":
Behavior3/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 of behavioral disclosure. It adds useful context by stating the prerequisite that the job must be COMPLETED, which isn't obvious from the schema alone. However, it lacks details on error handling, return format, or potential side effects, leaving gaps in behavioral understanding for a tool that retrieves data.

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 extremely concise and front-loaded, consisting of just one sentence that directly states the tool's function and key usage condition. Every word earns its place, with no redundant or unnecessary information, making it efficient and easy to understand.

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

Completeness3/5

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

Given the tool's moderate complexity (retrieving results based on a status condition), no annotations, and no output schema, the description is somewhat complete but has gaps. It covers the core purpose and a critical usage constraint, but lacks details on return values, error cases, or how results are structured, which could hinder an agent's ability to use it effectively without additional context.

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

Parameters3/5

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

The schema description coverage is 100%, with the parameter 'jobExecutionId' fully documented in the schema. The description doesn't add any additional meaning or details about the parameter beyond what the schema provides, such as format examples or constraints. This meets the baseline score of 3 since the schema handles the parameter documentation effectively.

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 tool's purpose: retrieving results for completed job executions. It specifies the verb 'get' and the resource 'results of a completed job execution,' making the function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_job_status' or 'get_job_audit_log,' which might handle related but different data.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: only when a job's status is COMPLETED. This implies that alternatives like 'get_job_status' should be used to check status first. However, it doesn't explicitly name these alternatives or detail when not to use this tool beyond the status requirement, such as for ongoing or failed jobs.

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/Moenamatics/Opus-MCP'

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