Skip to main content
Glama

apex_execute

Execute Apex REST requests in Salesforce to call custom endpoints and manage data using HTTP methods like GET, POST, PATCH, and DELETE.

Instructions

Executes an Apex REST request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe Apex REST endpoint to call (e.g., '/MyApexClass')
methodNoThe HTTP method (default: 'GET')GET
dataNoData for POST/PATCH requests

Implementation Reference

  • Registration of the apex_execute tool, including its description and JSON schema for input validation (action required, optional method and data).
    types.Tool(
        name="apex_execute",
        description="Executes an Apex REST request",
        inputSchema={
            "type": "object",
            "properties": {
                "action": {
                    "type": "string",
                    "description": "The Apex REST endpoint to call (e.g., '/MyApexClass')",
                },
                "method": {
                    "type": "string",
                    "description": "The HTTP method (default: 'GET')",
                    "enum": ["GET", "POST", "PATCH", "DELETE"],
                    "default": "GET",
                },
                "data": {
                    "type": "object",
                    "description": "Data for POST/PATCH requests",
                    "properties": {},
                    "additionalProperties": True,
                },
            },
            "required": ["action"],
        },
    ),
  • Handler for the apex_execute tool: validates inputs, calls Salesforce simple-salesforce library's apeXecute method on the action endpoint with optional method and data, and returns the JSON-formatted result.
    elif name == "apex_execute":
        action = arguments.get("action")
        method = arguments.get("method", "GET")
        data = arguments.get("data")
    
        if not action:
            raise ValueError("Missing 'action' argument")
        if not sf_client.sf:
            raise ValueError("Salesforce connection not established.")
    
        results = sf_client.sf.apexecute(action, method=method, data=data)
        return [
            types.TextContent(
                type="text",
                text=f"Apex Execute Result (JSON):\n{json.dumps(results, indent=2)}",
            )
        ]
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 'Executes an Apex REST request', implying a mutation operation that could have side effects, but doesn't specify authentication needs, rate limits, error handling, or what the execution entails (e.g., whether it's synchronous/asynchronous). This is a significant gap for a tool with potential write operations.

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 with zero waste. It's front-loaded and appropriately sized for the tool's complexity, 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 complexity (executing REST requests with potential side effects), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, response format, or error cases, which are crucial for safe and effective use in a Salesforce/Apex 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?

Schema description coverage is 100%, so the input schema fully documents the parameters (action, method, data). The description adds no additional meaning beyond what the schema provides, such as examples of Apex endpoints or data formats. Baseline 3 is appropriate since the schema does the heavy lifting.

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 'Executes an Apex REST request' clearly states the action (execute) and resource (Apex REST request), but it's vague about what this means in practice. It doesn't distinguish this tool from sibling tools like 'restful' or 'tooling_execute', which likely handle similar REST operations in the Salesforce context.

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 doesn't mention prerequisites, context, or exclusions, leaving the agent to guess based on tool names alone. For example, it's unclear when to choose this over 'restful' or 'tooling_execute' among the siblings.

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/leilaabdel/MCP-Salesforce'

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