Skip to main content
Glama
Sign In
Salesforce MCP Server

Salesforce MCP Server

by sudhakar6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

sf_query

Run a SOQL query and get all matching records in one response, automatically following pagination links to bypass row limits.

Instructions

Run a SOQL query and return matching records.

Follows nextRecordsUrl automatically so the full result set is returned in one call, regardless of Salesforce's per-page row limit.

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": {
      "soql": "<soql>"
    },
    "name": "sf_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
soqlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/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 discloses an important behavior: automatic following of nextRecordsUrl to return the full result set despite Salesforce page limits. This goes beyond what a basic 'run query' description would provide.

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 concise, front-loaded with the primary purpose, and uses a second sentence for an important behavioral detail. Every sentence earns its place.

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

Completeness4/5

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

For a single-parameter tool with no output schema, the description covers the core invocation detail and the key pagination behavior. It is slightly incomplete around when to prefer sf_bulk_query for very large result sets, but otherwise adequate.

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

Parameters2/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 little to compensate. It mentions 'SOQL query' but provides no examples, syntax hints, constraints, or additional meaning for the 'soql' parameter beyond its name.

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

Purpose4/5

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

The description uses a specific verb ('Run a SOQL query') and names the resource and outcome ('return matching records'). It is clear about what the tool does, though it does not explicitly differentiate itself from siblings like sf_search or sf_bulk_query.

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 about when to use this tool versus alternatives such as sf_search or sf_bulk_query. The description provides no context for choosing between the query, search, or bulk query tool.

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