list_concepts
List all 40 AgentForce concepts in this knowledge graph.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Salesforce AgentForce CKG
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It does not disclose any behavioral traits such as being read-only, potential performance implications, or any side effects. The action 'List' implies reading, but this is not explicitly stated.
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 a single sentence of 8 words, front-loaded with the key information. No unnecessary words or details.
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 list tool with no parameters and an output schema present, the description adequately states the action and scope. However, it could mention that it returns the full list without any filtering, which would further distinguish it from similar tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters, and the input schema coverage is 100% (vacuously). According to guidelines, 0 parameters gives a baseline of 4. The description doesn't need to add parameter info, so this 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 verb 'List', the resource 'concepts', and the scope 'all 40 AgentForce concepts in this knowledge graph'. It is specific and distinguishes itself from sibling tools like search_concepts, which implies a different purpose.
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?
The description provides no guidance on when to use this tool versus alternatives such as search_concepts or query_ckg. There is no mention of when not to use it or context about prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.1/5.0
Disambiguation4/5
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.
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness5/5
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.