Skip to main content
Glama
smn2gnt

MCP Salesforce Connector

by smn2gnt

apex_execute

Execute Apex REST requests to interact with Salesforce data by specifying endpoints, HTTP methods, and data payloads for streamlined integration and automation.

Instructions

Executes an Apex REST request

Input Schema

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

Implementation Reference

  • Handler implementation for the 'apex_execute' tool within the tool dispatch function. Extracts arguments, validates, calls Salesforce's apeExecute method, 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)}",
            )
        ]
  • Registration of the 'apex_execute' tool in the list_tools() function, including name, description, and input schema definition.
    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"],
        },
    ),
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions execution but fails to detail critical aspects like authentication requirements, rate limits, error handling, or what happens upon execution (e.g., side effects, response format). This leaves significant gaps for a tool that performs REST 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 wasted words. It is appropriately sized and front-loaded, making it easy to parse quickly without unnecessary elaboration.

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 REST requests, no annotations, and no output schema, the description is incomplete. It doesn't explain return values, error conditions, or behavioral nuances, making it inadequate for an agent to fully understand how to use this tool effectively.

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 already documents all parameters (action, data, method) with descriptions and enums. The description adds no additional meaning beyond what the schema provides, such as examples or constraints, resulting in a baseline score of 3.

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), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'restful' or 'tooling_execute', which likely handle similar REST operations, leaving the distinction vague.

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 such as 'restful' or 'tooling_execute'. The description lacks context about prerequisites, typical use cases, or exclusions, offering minimal help for an agent to choose correctly among 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

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

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