Skip to main content
Glama
ampcome-mcps

MCP Salesforce Connector

by ampcome-mcps

apex_execute

Execute custom Apex REST endpoints to interact with Salesforce data and business logic through 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

  • Handler function for 'apex_execute' tool. Extracts action, method, and data from arguments, validates, connects to Salesforce if needed, executes the Apex REST request using sf_client.sf.apexecute, and returns the JSON results.
    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)}",
            )
        ]
  • Registration of the 'apex_execute' tool in the list_tools handler, including its name, description, and input schema definition for action, method, and data parameters.
    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"],
        },
    ),
  • JSON schema defining the input parameters for the 'apex_execute' tool: required 'action' string, optional 'method' enum, optional 'data' object.
    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"],
    },

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior1/5

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

With no annotations, the description carries full burden for behavioral disclosure. It does not mention whether the operation is destructive, idempotent, or requires specific permissions, leaving critical traits unknown.

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

Conciseness4/5

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

The description is very short (6 words) and to the point. While it could be more informative, it wastes no words and is appropriate for a simple tool.

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 omits crucial context such as return format, error behavior, and prerequisites (e.g., Apex class must be exposed). This inadequately prepares an agent to use the tool correctly.

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 coverage is 100% and already defines all three parameters. The description adds no additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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 'Executes an Apex REST request' clearly identifies the verb and resource, distinguishing it from generic REST or tooling operations among siblings. However, it lacks explicit context that this refers to Salesforce Apex classes.

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 like 'restful' or 'tooling_execute'. The agent has no information about prerequisites or preferred scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.