Skip to main content
Glama
Sign In
MCP_Salesforce

MCP_Salesforce

by waaljair
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_accounts

Find Salesforce accounts by name, industry, or custom criteria. Retrieve matching records with configurable result limits.

Instructions

Search for Salesforce accounts by name, industry, or other criteria

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": {
      "query": "<query>"
    },
    "name": "search_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default: 10)
queryYesSearch query for account name or other fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It adds context that the search supports name, industry, or other criteria, but it does not disclose return format, pagination, ordering, or confirm the read-only nature explicitly. The read operation is implied by the verb 'search'.

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 sentence of 11 words, front-loaded with the verb 'search'. Every word adds value with no redundancy, making it perfectly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple search tool with no output schema and no annotations, the description provides the core purpose but omits what the tool returns (e.g., list of account records). It is adequate but not fully complete for an agent to know exactly what to expect.

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% with descriptions for both query and limit. The description adds 'industry' as an example field, but this is minor enhancement over the schema's 'account name or other fields'. Baseline 3 is appropriate.

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 it searches Salesforce accounts, with the verb 'search' and specific resource 'Salesforce accounts'. This unambiguously distinguishes it from sibling tools like search_contacts or search_opportunities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for searching accounts but does not explicitly discuss when to use this tool versus alternatives like search_contacts or search_leads. No exclusion or alternative tool is mentioned, so guidance is implied rather than explicit.

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