Skip to main content
Glama

list_kg_context_configs

Read-only

Lists Knowledge Graph grounding configurations used by Now Assist and AI agents, including graphs, context configs, connector maps, and use-case mappings.

Instructions

List Knowledge Graph configuration used by Otto (Now Assist) and AI agents for grounding: graphs (sys_meta_graph), context configs (sn_kg_context_config), related-data connector maps (sn_kg_related_data_map) and use case mappings (knowledge_graph_use_case_mapping).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_kg_context_configs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows per section (default 50)
include_configurationNoInclude full JSON configuration of context configs (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description's real contribution is disclosing that results span four distinct sections/tables, which an agent could not guess from the schema alone; however, it says nothing about how sections are returned, ordering, or truncation 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?

A single front-loaded sentence puts the verb and resource first, then the covered tables. It is dense but each clause carries information; the parenthetical table identifiers are the only borderline-verbose element, though they aid grounding.

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?

With no output schema, the description usefully names the categories of rows returned, which is the minimum an agent needs. It still omits the shape of the combined response across sections and how limit interacts with multiple sections, leaving a moderate gap for a multi-section listing tool.

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 both parameters (limit, include_configuration) fully described including defaults, so the baseline of 3 applies. The description adds no further meaning about these parameters—notably it never mentions that limit applies per section or what the full JSON configuration looks like.

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 opens with a specific verb+resource ('List Knowledge Graph configuration') and enumerates the four underlying tables it spans (sys_meta_graph, sn_kg_context_config, sn_kg_related_data_map, knowledge_graph_use_case_mapping), which makes the scope unambiguous. It does not differentiate itself from nearby siblings such as describe_kg_schema, so it stops short of a 5.

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 explains who consumes this config (Otto/Now Assist and AI agents for grounding) but never states when an agent should call this versus an alternative such as describe_kg_schema. There are no exclusions, prerequisites, or routing hints, leaving selection entirely to inference from the tool name.

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