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

sf-docs-mcp

by Avinava
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sf_graph_query

Navigate the Salesforce Knowledge Graph: find cross-referenced docs, list Apex namespaces, explore service categories, get full document context, or search by keyword.

Instructions

Navigate the Salesforce Knowledge Graph. Find related docs, explore namespaces, discover service categories, or get full context for a document.

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": {
      "action": "<action>"
    },
    "name": "sf_graph_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction: 'related' (find cross-referenced docs), 'namespace' (list docs in an Apex namespace), 'service' (list domains in a service category), 'context' (get full doc context), 'search' (keyword search)
nodeIdNoDocument node ID for 'related' or 'context' (e.g. 'doc:apex-reference:apex_methods_system_string')
keywordNoKeyword for 'search' action
serviceNoService category for 'service' action (e.g. 'analytics', 'commerce', 'industries')
namespaceNoNamespace name for 'namespace' action (e.g. 'System', 'ConnectApi')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It suggests a read-only navigation tool but never explicitly states this or covers return format, error behavior, pagination, or other side effects. It essentially describes purpose, not behavior.

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 compact, front-loaded with the key concept, and uses a clear second sentence to list capabilities. It omits the 'search' action, but the text is appropriately concise and free of filler.

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?

This is a five-parameter tool with no output schema or annotations, and the description only highlights four capabilities, leaving the 'search' action unsupported. It gives no hints about return values or action-specific combinations, though the schema fills in parameter meaning. It is minimally viable but not fully complete for an agent navigating complex graph queries.

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 schema describes all five parameters with 100% coverage, including an enum for actions and specific examples for nodeId, service, and namespace. This matches the baseline of 3 for high schema coverage; the description adds no further parameter-level detail, but the schema already provides adequate semantics.

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 identifies a clear domain ('Salesforce Knowledge Graph') and lists four concrete operations: finding related docs, exploring namespaces, discovering service categories, and getting full context. This indicates a distinct graph-navigation resource, though it omits the 'search' action present in the schema and does not explicitly differentiate from sibling search tools.

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 context by naming scenarios like exploring namespaces and service categories, but it gives no explicit guidance on when to prefer this tool over siblings such as sf_search or sf_semantic_search, nor does it state any exclusions. The multi-action enumeration provides some context but stops short of clear alternatives.

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