Skip to main content
Glama
Sign In
Salesforce MCP Server

Salesforce MCP Server

by LokiMCPUniverse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

salesforce_search

Search Salesforce records across multiple objects using SOSL queries. Find data matching keywords in a single operation.

Instructions

Execute a SOSL (Salesforce Object Search Language) search.

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": {
      "search_query": "<search_query>"
    },
    "name": "salesforce_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNo
search_queryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
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 but adds no behavioral context. It doesn't mention read-only nature, object scope, limits, or error conditions, which is a significant gap for a search tool.

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 a single, front-loaded sentence with no redundancy. However, its brevity borders on under-specification, so it earns a 4 rather than a 5.

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?

Despite having an output schema, the description is too thin to be complete. It omits usage guidelines, parameter semantics, and any behavioral nuances, leaving critical decisions to the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain either parameter. 'Search Query' and 'Org' remain undefined except by their names, so the agent gains no added meaning.

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 tool executes a SOSL search, with a specific verb ('execute') and resource ('SOSL'). The acronym expansion distinguishes it from salesforce_query, which presumably handles SOQL.

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 given on when to use this tool versus alternatives like salesforce_query or other siblings. It merely states the action, leaving the agent to infer applicability.

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

Deploy Server

Other Tools