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"],
    },
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 mentions 'executes' but doesn't clarify authentication requirements, rate limits, error handling, or what happens upon execution (e.g., side effects, response format). For a tool that likely interacts with Salesforce APIs, this is a significant gap in transparency.

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: 'Executes an Apex REST request'. It's front-loaded with the core action and resource, with zero wasted words, making it highly concise and well-structured for quick understanding.

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 of executing Apex REST requests (likely involving Salesforce custom code), no annotations, no output schema, and multiple sibling tools, the description is incomplete. It doesn't explain return values, error cases, or how it differs from similar tools, leaving critical context gaps 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 clear documentation for 'action', 'method', and 'data' parameters. The description adds no additional meaning beyond the schema, such as examples of Apex endpoints or data formatting. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 'Executes an Apex REST request', which clearly indicates it performs an execution action on Apex REST endpoints. However, it lacks specificity about what Apex REST is (Salesforce custom API) and doesn't distinguish it from sibling tools like 'restful' or 'tooling_execute', making it somewhat vague for users unfamiliar with Salesforce terminology.

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. With siblings like 'restful' (likely for standard REST calls) and 'tooling_execute' (likely for Tooling API), the description offers no context on use cases, prerequisites, or exclusions, leaving users to guess based on tool names 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/ampcome-mcps/salesforce-mcp'

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