Skip to main content
Glama

Dump Configurations

dump_configurations

Retrieve, filter, and summarize Ambari service configuration types and key-value pairs in one call, with limits and optional truncation for safe bulk introspection.

Instructions

Unified configuration introspection tool (supersedes get_configurations & list_configurations & dump_all_configurations).

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": "dump_configurations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax number of types to output in bulk mode (0 = unlimited)
filterNosubstring applied to type names OR property keys
max_charsNotruncate final output if exceeds
summarizeNobulk mode summary lines only (counts + sample keys, forces include_values False)
config_typeNofocus on one type's latest tag (other bulk params ignored except filter on keys)
include_valuesNoinclude key=value pairs (bulk/full mode only)
service_filterNosubstring to restrict bulk types (ignored if config_type provided)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv3.8.2
    • addedInput schema / properties / config_type / description
      Added value: +"focus on one type's latest tag (other bulk params ignored except filter on keys)"
    • addedInput schema / properties / filter / description
      Added value: +"substring applied to type names OR property keys"
    • addedInput schema / properties / include_values / description
      Added value: +"include key=value pairs (bulk/full mode only)"
    • addedInput schema / properties / limit / description
      Added value: +"max number of types to output in bulk mode (0 = unlimited)"
    • addedInput schema / properties / max_chars / description
      Added value: +"truncate final output if exceeds"
    • addedInput schema / properties / service_filter / description
      Added value: +"substring to restrict bulk types (ignored if config_type provided)"
    • addedInput schema / properties / summarize / description
      Added value: +"bulk mode summary lines only (counts + sample keys, forces include_values False)"
  2. Changed10 schema fields changedv3.7.5
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / config_type / title
      Removed value: -"Config Type"
    • removedInput schema / properties / filter / title
      Removed value: -"Filter"
    • removedInput schema / properties / include_values / title
      Removed value: -"Include Values"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / max_chars / title
      Removed value: -"Max Chars"
    • removedInput schema / properties / service_filter / title
      Removed value: -"Service Filter"
    • removedInput schema / properties / summarize / title
      Removed value: -"Summarize"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"_WrappedResult"
  3. First observed

TDQS

C2.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 the full behavioral burden, yet it discloses nothing: no read-only confirmation, no mention of truncation via max_chars, no explanation of the bulk-vs-single-type modes exposed by config_type/summarize/include_values. The interesting behavioral traits live only in the schema parameter descriptions, not the tool description.

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 with no filler; the supersedes note is compact and useful. It is efficient, though the extreme brevity edges into under-specification rather than ideal conciseness.

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?

For a 7-parameter tool with multiple distinct operating modes (bulk dump, single-type focus, summarized counts, value inclusion) and no annotations, a one-sentence description is inadequate. The output schema exists, so return values need not be described, but the mode-selection logic and read-only nature are missing.

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 description coverage is 100%, so the schema already documents all seven parameters (limited, filter, max_chars, summarize, config_type, include_values, service_filter) with defaults. The description adds no meaning beyond that, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description labels it a 'configuration introspection tool' and names three tools it supersedes, which helps disambiguation, but 'introspection' is vague about what actually happens (dumping config types, keys, and values). The name 'dump' implies bulk retrieval, but the description never states the operation concretely, so an agent must infer purpose from the schema.

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 only usage signal is that it supersedes get_configurations/list_configurations/dump_all_configurations, which none of the listed siblings include. There is no guidance on when to use the bulk mode vs a single config_type, when to set summarize, or how it relates to any of the actual sibling tools.

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