Skip to main content
Glama
Moenamatics

Opus MCP Server

by Moenamatics

get_workflow_details

Retrieve workflow details including required input schema to understand job requirements before execution in the Opus automation platform.

Instructions

Get workflow details including jobPayloadSchema that defines required inputs for a workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdYesThe ID of the workflow to retrieve details for

Implementation Reference

  • The main handler function for the get_workflow_details tool. It extracts the workflowId from arguments, makes a GET request to the Opus API endpoint `/workflow/${workflowId}`, and returns the response data as a formatted JSON text content block.
    private async getWorkflowDetails(args: any) {
      const { workflowId } = args;
      const response = await this.axiosInstance.get(
        `/workflow/${workflowId}`
      );
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • The input schema definition for the get_workflow_details tool, specifying that a workflowId string is required.
    inputSchema: {
      type: "object",
      properties: {
        workflowId: {
          type: "string",
          description: "The ID of the workflow to retrieve details for",
        },
      },
      required: ["workflowId"],
    },
  • src/index.ts:115-129 (registration)
    The tool registration object for get_workflow_details in the getTools() method, which lists all available tools for the MCP server. Includes name, description, and input schema.
    {
      name: "get_workflow_details",
      description:
        "Get workflow details including jobPayloadSchema that defines required inputs for a workflow",
      inputSchema: {
        type: "object",
        properties: {
          workflowId: {
            type: "string",
            description: "The ID of the workflow to retrieve details for",
          },
        },
        required: ["workflowId"],
      },
    },
  • src/index.ts:80-81 (registration)
    The switch case in the CallToolRequestSchema handler that dispatches calls to the get_workflow_details tool by invoking the getWorkflowDetails method.
    case "get_workflow_details":
      return await this.getWorkflowDetails(args);
Behavior2/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 states this is a 'Get' operation, implying it's read-only, but doesn't confirm safety aspects like whether it requires authentication, has rate limits, or what happens if the workflowId is invalid. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, efficient sentence that directly states the tool's purpose. It's front-loaded with the core action and includes a key detail (jobPayloadSchema) without unnecessary elaboration. Every word earns its place, making it highly concise and well-structured.

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 low complexity (one parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and hints at the return content (jobPayloadSchema), but lacks context on usage, behavioral traits, or output structure. Without annotations or output schema, the agent has incomplete information for effective use.

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?

Schema description coverage is 100%, with the single parameter 'workflowId' fully documented in the schema. The description adds no additional parameter details beyond what the schema provides (e.g., format examples or constraints). According to the rules, with high schema coverage, the baseline is 3 even without param info in the description.

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 the resource 'workflow details', specifying that it retrieves information including the jobPayloadSchema. It distinguishes itself from siblings like execute_job or get_job_status by focusing on workflow metadata rather than job execution or status. However, it doesn't explicitly contrast with all siblings (e.g., get_job_audit_log).

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. It doesn't mention prerequisites (e.g., needing a workflowId), exclusions, or comparisons to siblings like get_job_results or initiate_job. The agent must infer usage from the tool name and description alone.

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