Skip to main content
Glama
Sign In
sf-docs-mcp

sf-docs-mcp

by Avinava
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sf_explain_error

Explain Salesforce error messages by searching official documentation. Discover common causes and resolution steps.

Instructions

Explain a Salesforce error message or exception. Searches documentation for the error, provides explanation, common causes, and resolution steps.

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": {
      "error": "<error>"
    },
    "name": "sf_explain_error"
  }
}

Input Schema

NameRequiredDescriptionDefault
errorYesError message or exception (e.g. 'UNABLE_TO_LOCK_ROW', 'System.LimitException', 'FIELD_CUSTOM_VALIDATION_EXCEPTION')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4/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. It discloses that the tool searches documentation and provides explanation, common causes, and resolution steps. This is meaningful behavioral context, though it omits caveats like accuracy or access requirements.

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 two concise sentences that front-load the primary purpose and then quickly explain the tool's process and output. Every word 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 simple one-parameter tool with no output schema, the description is complete enough: it states what the tool does and what it returns (explanation, causes, resolution steps). It could add more detail on output formatting or search scope, but it covers the essentials.

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 input schema fully documents the single required parameter with examples, and schema description coverage is 100%. The description adds no additional parameter-specific detail beyond what the schema provides, so the baseline of 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 uses a specific verb ('Explain') and resource ('Salesforce error message or exception'), and the focus on error diagnosis clearly distinguishes it from sibling tools like sf_search or sf_semantic_search.

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 when to use the tool (when you encounter a Salesforce error to explain), but it does not explicitly state when to use it over alternatives or provide exclusions. Context is clear but 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