MCP_Salesforce

create_contact

Create a Salesforce contact with fields for name, email, phone, title, and mailing address. Adds customer data to your CRM.

Instructions

Create a new Salesforce contact

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lastName": "<lastName>"
    },
    "name": "create_contact"
  }
}

Input Schema

Name	Required	Description
`email`	No	Contact email address
`phone`	No	Contact phone number
`title`	No	Contact job title
`lastName`	Yes	Contact last name (required)
`accountId`	No	Associated account ID
`firstName`	No	Contact first name
`department`	No	Contact department
`description`	No	Contact description
`mailingCity`	No	Mailing city
`mailingState`	No	Mailing state/province
`mailingStreet`	No	Mailing street address
`mailingCountry`	No	Mailing country
`mailingPostalCode`	No	Mailing postal code

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description must alone convey behavior, but it only states the bare action. It does not disclose that lastName is required, what the API returns on success/failure, or any side effects like creating a record in the CRM. No contradictions, but significantly under-informative.

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, clear, front-loaded sentence with no extraneous words. It perfectly captures the core purpose without redundancy, though it sacrifices depth for brevity.

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?

For a tool with 13 parameters and no output schema or annotations, the one-sentence description is grossly insufficient. It doesn't mention that only lastName is required, potential relationships (accountId), or what the response looks like. The schema lists fields but does not explain the tool's overall 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?

The description adds no parameter information, but the input schema provides 100% coverage with descriptions for all 13 parameters, including the required lastName. Per the rubric, high schema coverage establishes a baseline of 3.

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

Purpose5/5

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

The description clearly states the action (create) and the resource (Salesforce contact), making it easy to distinguish from sibling tools like update_contact or search_contacts. It is specific and unambiguous.

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 gives no guidance on when to use this tool versus alternatives (e.g., search_contacts to find an existing contact, update_contact to modify). It also omits any prerequisites, such as requiring an existing account for accountId.

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

Deploy Server