Skip to main content
Glama

load_execution_info

Retrieve detailed requirements and inputs for specific workflows or operations, enabling informed action execution. Save configuration data to 'jentic.json' for streamlined coding agent integration.

Instructions

Get more details about a specific action (like what information it needs from the user) before confirming you want to run it. Usually used if the action requires specific inputs. Coding Agents: To provide tools to an LLM that you have selected at runtime, use this tool to retrieve the necessary information and save it to 'jentic.json' at the root of your project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operation_uuidsYesThe UUIDs of the operations to include in the configuration files.
workflow_uuidsYesThe UUIDs of the workflows to include in the configuration files.

Implementation Reference

  • Core handler function for the 'load_execution_info' tool. Extracts workflow_uuids and operation_uuids from the request, combines them into ids for LoadRequest, calls self.jentic.load(), and returns the result or an error response.
    async def generate_runtime_config(self, request: dict[str, Any]) -> dict[str, Any]:
        """MCP endpoint for generating a configuration file from a selection set.
    
        Args:
            request: MCP tool request parameters.
    
        Returns:
            MCP tool response.
        """
        # Get the workflow and operation UUIDs from the request
        workflow_uuids = request.get("workflow_uuids", [])
        if isinstance(workflow_uuids, str):
            workflow_uuids = [workflow_uuids]
        operation_uuids = request.get("operation_uuids", [])
        if isinstance(operation_uuids, str):
            operation_uuids = [operation_uuids]
        
        # Get the API name or use empty string as default
        api_name = request.get("api_name", "")
    
        logger = logging.getLogger(__name__)
        logger.debug(
            f"Generating config with workflow_uuids: {workflow_uuids}, operation_uuids: {operation_uuids}, api_name: {api_name}"
        )
    
        try:
            # In generate_runtime_config method replace load_execution_info call
            load_request = LoadRequest(
                ids=workflow_uuids + operation_uuids,
            )
            load_response = await self.jentic.load(load_request)
            result = load_response.model_dump(exclude_none=False)
            return {"result": result}
    
        except ValueError as e:
            logger.error(f"Error generating config: {str(e)}")
            return {
                "result": {
                    "success": False,
                    "operation_uuids": operation_uuids,
                    "workflow_uuids": workflow_uuids,
                    "api_name": api_name,
                    "message": str(e),
                    "config": {},
                }
            }
  • Tool schema definition for 'load_execution_info', including description, input parameters (workflow_uuids array required, operation_uuids array required, api_name optional), used in tool lists and MCP initialization.
    LOAD_CONFIG_TOOL = {
        "name": "load_execution_info",
        "description": (
            "Get more details about a specific action (like what information it needs from the user) before confirming you want to run it. "
            "Usually used if the action requires specific inputs. "
            "Coding Agents: To provide tools to an LLM that you have selected at runtime, use this tool to retrieve the necessary information and save it to 'jentic.json' at the root of your project."
        ),
        "parameters": {
            "type": "object",
            "properties": {
                "workflow_uuids": {
                    "type": "array",
                    "items": {"type": "string"},
                    "description": "The UUIDs of the workflows to include in the configuration files.",
                },
                "operation_uuids": {
                    "type": "array",
                    "items": {"type": "string"},
                    "description": "The UUIDs of the operations to include in the configuration files.",
                },
                "api_name": {
                    "type": "string",
                    "description": "The API name of the workflows to include in the configuration files."
                },
            },
            "required": ["workflow_uuids", "operation_uuids"],
        },
    }
  • Registers 'load_execution_info' tool to call mcp_adapter.generate_runtime_config in the central handle_request function.
    tool_handlers = {
        "search_apis": mcp_adapter.search_api_capabilities,
        "load_execution_info": mcp_adapter.generate_runtime_config,
        "execute": mcp_adapter.execute,  # Add the execute tool handler
        "submit_feedback": mcp_adapter.submit_feedback
    }
  • Registers 'load_execution_info' to self.adapter.generate_runtime_config for JSON-RPC tools/call handling.
    tool_handlers = {
        "search_apis": self.adapter.search_api_capabilities,
        "load_execution_info": self.adapter.generate_runtime_config,
        "execute": self.adapter.execute,
        "submit_feedback": self.adapter.submit_feedback,
    }
  • Registers 'load_execution_info' to wrapper method self._handle_generate_runtime_from_selection_set (which delegates to adapter.generate_runtime_config) for stdio transport.
    self._handlers = {
        "search_apis": self._handle_search_api_capabilities,
        "load_execution_info": self._handle_generate_runtime_from_selection_set,
        "generate_code_sample": self._handle_generate_code_sample,
        "execute": self._handle_execute,  # Add execute handler
        "submit_feedback": self._handle_submit_feedback, # Add submit_feedback handler
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers limited behavioral insight. It mentions retrieving information and saving to a file, but doesn't disclose critical traits like whether this is a read-only operation, if it modifies state, authentication needs, rate limits, or error handling. The description adds some context but leaves significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately concise but not optimally structured. The first sentence clearly states the purpose, but the second sentence adds implementation details for coding agents that may not apply to all users. The information is somewhat front-loaded but could be more focused.

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 no annotations and no output schema, the description should provide more complete context. It mentions retrieving details and saving to a file, but doesn't explain what format the details take, what 'jentic.json' contains, or what happens if parameters are invalid. For a tool with 2 required parameters and mutation implications, this is inadequate.

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%, so parameters are well-documented in the schema. The description doesn't add meaningful semantic context beyond what the schema provides about operation_uuids and workflow_uuids. It mentions 'configuration files' but doesn't clarify how parameters relate to this output.

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

Purpose3/5

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

The description states the tool 'Get more details about a specific action' which indicates its purpose, but it's vague about what 'details' means and doesn't clearly differentiate from sibling tools like 'execute' or 'search_apis'. It mentions saving to 'jentic.json' which adds specificity but confuses the core purpose with implementation details for coding agents.

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 some guidance ('Usually used if the action requires specific inputs') but lacks explicit when-to-use vs. alternatives. It doesn't clarify when to choose this over 'execute' or 'search_apis', and the coding agent note is situational rather than general usage guidance.

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

Related 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/jentic/jentic-sdks'

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