Skip to main content
Glama

Salesforce

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Sf Get Record

sf_get_record
Read-onlyIdempotent

Fetch a single Salesforce record by ID. Specify object type (e.g., 'Account', 'Contact', 'Opportunity') and record ID. Returns all fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSalesforce record ID
fieldsNoComma-separated field names (optional)
objectYesSObject type (e.g., "Account", "Contact", "Opportunity")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
IdNoSalesforce record ID
errorNoError code if request failed
messageNoError message if request failed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "Id": {
+      "description": "Salesforce record ID",
+      "type": "string"
+    },
+    "error": {
+      "description": "Error code if request failed",
+      "type": "string"
+    },
+    "message": {
+      "description": "Error message if request failed",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "001xx000003DHP",
+    "object": "Account"
+  },
+  {
+    "fields": "Id,FirstName,LastName,Email",
+    "id": "003xx000004TM1",
+    "object": "Contact"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds that it returns all fields, which is consistent and provides output clarity. No contradictions.

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?

Two sentences front-load the purpose, no wasted words. Extremely concise.

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?

Given rich annotations, output schema, and examples, the description is largely complete. It lacks explicit mention of optional fields parameter behavior but is adequate for a simple read operation.

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 each parameter. The description mentions object and ID but adds no new meaning beyond the schema. 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 the tool fetches a single Salesforce record by ID and object type, with examples. It distinguishes from siblings like sf_query or sf_search by focusing on single record retrieval.

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 single record retrieval by ID but gives no explicit guidance on when to use versus alternatives (e.g., sf_query, sf_search) or when not to use.

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

All Salesforce toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources