Salesforce AgentForce CKG
Server Details
Salesforce AgentForce knowledge graph — 40 nodes, Einstein Trust Layer, 11x fewer tokens than RAG.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 13.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Server Listing
- ckg-agentforce
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 10 tools
Most tools serve clearly distinct roles: querying, searching, routing, and verification are separate concerns. However, query_ckg and get_prerequisites both return prerequisite information, which could cause an agent to select the wrong tool when a simple prerequisite list is needed. The descriptions do clarify the difference (generic traversal vs. full ordered chain), but some ambiguity remains.
The vast majority of tools follow a consistent snake_case verb_noun pattern, such as evaluate_trust_chain, list_concepts, and route_query. The only exception is resolution_path, which is a noun phrase rather than a verb_noun, making it slightly less predictable. This is a minor deviation from an otherwise strong pattern.
With 10 tools, the server has a well-scoped surface area for a knowledge graph that requires discovery, traversal, routing, and audit capabilities. Each tool represents a distinct operation, and there are no redundant or unnecessary entries. This falls comfortably within the ideal range for a domain-specific server.
The toolset covers the full read-side lifecycle of the knowledge graph: discovery, traversal, path analysis, routing, and trust verification. It also includes specialized tools for benchmarking and source verification, which are unusual but valuable additions. No obvious critical gaps exist, such as missing search or traversal capabilities.
Available Tools
10 toolsevaluate_trust_chainAInspect
Return a machine-readable JSON trust chain + ROI analysis + payment recommendation.
Designed for autonomous agent consumption. The agent reads the JSON, evaluates the ROI gate, selects the cheapest positive-ROI payment option, and purchases autonomously if budget is pre-authorized.
Trust chain closes the audit gap that RAG cannot: source_hashes → SHA-256 of source docs (what was known at extraction time) graph_hash → SHA-256 of the installed graph file (what is declared now) signer_key_id → Ed25519 public key fingerprint (who is attesting) benchmark_receipt → BoundaryAttest-signed F1 claim (cryptographic performance proof) scitt_status → SCITT ledger submission status (public audit anchor)
ROI gate: if total_value_per_call_usd > payment_option.price_per_call_usd → autonomous_pay = true.
Returns: JSON string (schema: ckg-trust-chain-v1).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
export_benchmark_receiptAInspect
Generate a signed BoundaryAttest receipt for the agentforce CKG benchmark result.
Produces a ckg.benchmark_result.exported claim signed with this server's Ed25519
session key. Any party holding the public key can verify the signature over the canonical
JSON claim. Implements GuardrailDecisionV1 · experimental-interop-v0.1.
Result: F1 0.471 over 30 queries · ckg-benchmark v0.6.2 · 4× over RAG baseline (0.123).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_prerequisitesAInspect
Return the full ordered prerequisite chain for an AgentForce concept.
Shows everything the concept depends on — the complete upstream path.
Args: concept: Target concept — e.g. 'Autonomous Resolution', 'Multi-LoRA Serving', 'Custom Actions', 'Semantic Retrieval'.
| Name | Required | Description | Default |
|---|---|---|---|
| concept | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
list_conceptsAInspect
List all 40 AgentForce concepts in this knowledge graph.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
query_ckgAInspect
Traverse the AgentForce knowledge graph from any concept.
Returns prerequisites (what this concept needs) and dependents (what it enables). Every relationship traces to an authoritative Salesforce doc URL.
Args: concept: Concept name — e.g. 'Autonomous Resolution', 'Einstein Trust Layer', 'Service Agent', 'Grounding', 'NVIDIA NIM'. depth: Traversal depth 1–5 (default 3).
| Name | Required | Description | Default |
|---|---|---|---|
| depth | No | ||
| concept | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
query_intersectAInspect
Answer a conjunctive query: concepts reachable from EVERY anchor at once (A AND B).
query_ckg walks outward from one concept. This intersects the reachable sets of two or more, which is the shape of most real questions — "the component that satisfies A AND applies to B". Neither anchor alone answers it; the answer lives in the overlap.
Every branch is an exact set of declared edges, so the intersection is exact. A concept appears only if a declared path reaches it from each anchor. A relation missing from the graph produces an empty result, never a guess.
Args:
branches: Two or more branches. Either a bare anchor ("TensorRT-LLM"), which takes
everything within depth hops, or an anchor plus an explicit relation path using
'>' ("TensorRT-LLM > REQUIRES > ENABLES"), where each relation replaces the
frontier. '*' matches any relation. Mix both forms freely.
depth: Hops for bare-anchor branches, 1-5 (default 2). Ignored for explicit paths.
direction: 'out' follows dependencies, 'in' follows them backwards, 'both' (default).
mode: 'AND' (default) intersects branches; 'OR' unions them.
limit: Max concepts listed, 1-200 (default 40). The true count is always shown.
Returns: Markdown with the query plan and its per-step set sizes, then the answer set with taxonomy tags. Reports which branch was empty when the intersection is empty.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | AND | |
| depth | No | ||
| limit | No | ||
| branches | Yes | ||
| direction | No | both |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
resolution_pathAInspect
Trace the exact path that determines an AgentForce autonomous resolution event.
This is the $2/resolution billing path — what the agent must traverse correctly to resolve autonomously without human handoff.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
route_queryAInspect
Route an AgentForce question to the optimal model and reasoning approach via graph depth.
The CKG graph IS the router. AgentForce dependency chains (e.g. Einstein Trust Layer → Data Cloud → NVIDIA NIM → Resolution Criteria) have typed hops that signal reasoning complexity deterministically. No heuristic: the graph decides.
Routing table: hop_depth 1 → haiku · direct (simple concept lookup) hop_depth 2 → sonnet · generic_cot (moderate chain) hop_depth 3+ → opus · sparql_cot (deep dependency, structured reasoning)
Args: question: Concept name or natural language question about Salesforce AgentForce.
Returns: model_tier + reasoning_approach + why + context subgraph to inject before LLM call.
| Name | Required | Description | Default |
|---|---|---|---|
| question | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
search_conceptsAInspect
Find AgentForce concepts by keyword.
Args: query: Search term — e.g. 'resolution', 'trust', 'grounding', 'action', 'NIM'.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
verify_sourceAInspect
Return the source URL and content hash for an AgentForce concept node.
Audit chain: edge answer → graph commit → source_hash → source_url (fetch hint)
Verification: curl -s <source_url> | sha256sum # compare output to source_hash
Args: concept: Concept label (partial match supported). receipt: If True, also return a signed BoundaryAttest receipt envelope (experimental-interop-v0.1) binding concept_label + source_url + source_hash + timestamp to this server's ed25519 session key.
| Name | Required | Description | Default |
|---|---|---|---|
| concept | Yes | ||
| receipt | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Added
query_intersect
9 tool updates
- First observed
evaluate_trust_chain - First observed
export_benchmark_receipt - First observed
get_prerequisites - First observed
list_concepts - First observed
query_ckg - First observed
resolution_path - First observed
route_query - First observed
search_concepts - First observed
verify_source
Related MCP Connectors
NVIDIA AI knowledge graphs — 20 domains. 4x F1, 11x fewer tokens, SHA-256 provenance. MCP-native.
NVIDIA NemoClaw knowledge graph — 55 nodes, F1 0.576 (+269% vs RAG), 11x fewer tokens. MCP-native.
Graph memory for AI agents: entities, cause-effect links, cross-session recall, time travel.
Graph-native persistent memory for AI agents — 33 MCP tools, zero-LLM writes.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceBuild Real-Time Knowledge Graphs for AI Agents32,620Apache 2.0
- AlicenseAqualityCmaintenanceEnables LLM agents to search, read, and query Salesforce documentation across 129 domains. Uses a pre-compiled knowledge graph with 53,000 nodes and 18,000 code snippets for instant retrieval without RAG.1216 npm4MIT
- AlicenseNot gradedqualityBmaintenanceSelf-evolving knowledge graph for AI agents — persistent memory that gets smarter with every interaction.Apache 2.0
- AlicenseAqualityBmaintenanceAssociative key-graph memory for LLM agents — recall facts by association (recall → read_key → read_memory) instead of vector similarity alone, with persistent cross-session memory and cross-lingual keys.10217 npm3MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.