iSuite Operations MCP Server

list_config_keys

List iSuite configuration keys to inspect available settings. Filter by section, include default or secret keys.

Instructions

List all available iSuite configuration keys, optionally filtered by section.

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_config_keys"
  }
}

Input Schema

Name	Required	Description
`section`	No	Config section prefix to filter by (e.g. 'database', 'scheduler', 'security').
`includeDefaults`	No	Include keys that are set to their default values (default true).
`includeSecrets`	No	Include secret/password keys (values will be masked, default false).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 13, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It does not disclose that the tool is read-only, safe to call, or any potential impacts like rate limits. Minimal behavioral context provided.

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?

Single sentence with no wasted words. Clear and direct.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given three parameters and no output schema or annotations, the description is too minimal. It omits details like return format, pagination, ordering, or examples, which are important for an agent to invoke correctly.

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%, so baseline is 3. The description only echoes the filtering by section; it adds no extra meaning for includeDefaults or includeSecrets beyond their schema descriptions.

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?

Description clearly states the tool lists config keys with optional filtering by section. The verb 'list' and resource 'configuration keys' are specific, distinguishing it from sibling tools like get_config_value or compare_configs.

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?

No explicit guidance on when to use this tool versus alternatives like get_config_value or compare_configs. Filtering by section is mentioned, but no context on when filtering is needed or when to avoid this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.