Skip to main content
Glama
HatriGt

HANA Cloud MCP Server

by HatriGt

hana_show_config

Display the current configuration of your HANA database to review settings and ensure proper setup.

Instructions

Show the HANA database configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'hana_show_config' tool. It logs the tool usage, retrieves the display configuration, formats it, and returns a formatted response.
    static async showConfig(args) {
      logger.tool('hana_show_config');
      
      const displayConfig = config.getDisplayConfig();
      const formattedConfig = Formatters.formatConfig(displayConfig);
      
      return Formatters.createResponse(formattedConfig);
    }
  • The tool definition object for 'hana_show_config', including its name, description, and empty input schema (no parameters required).
    {
      name: "hana_show_config",
      description: "Show the HANA database configuration",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • The TOOL_IMPLEMENTATIONS object maps the tool name 'hana_show_config' to its handler function ConfigTools.showConfig for execution via ToolRegistry.
    const TOOL_IMPLEMENTATIONS = {
      hana_show_config: ConfigTools.showConfig,
      hana_test_connection: ConfigTools.testConnection,
      hana_show_env_vars: ConfigTools.showEnvVars,
      hana_list_schemas: SchemaTools.listSchemas,
      hana_list_tables: TableTools.listTables,
      hana_describe_table: TableTools.describeTable,
      hana_list_indexes: IndexTools.listIndexes,
      hana_describe_index: IndexTools.describeIndex,
      hana_execute_query: QueryTools.executeQuery
    };
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 burden of behavioral disclosure. It states the tool shows configuration but doesn't describe what 'configuration' includes (e.g., settings, parameters, status), whether it's read-only or has side effects, or how results are formatted. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, efficient sentence with zero waste. It's front-loaded with the core purpose and uses clear language. Every word earns its place, making it easy to parse quickly.

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 the lack of annotations and output schema, the description is incomplete for a tool that likely returns configuration details. It doesn't specify what 'configuration' entails, potential output formats, or any behavioral traits. For a tool with no structured data to rely on, this minimal description fails to provide sufficient context for effective use.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to compensate for any gaps, and it appropriately doesn't mention parameters. A baseline of 4 is applied since no parameter information is required.

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 clearly states the tool's purpose as 'Show the HANA database configuration' with a specific verb ('Show') and resource ('HANA database configuration'). It distinguishes itself from siblings like hana_list_tables or hana_execute_query by focusing on configuration rather than data or structure. However, it doesn't explicitly differentiate from hana_show_env_vars, which might share conceptual similarity.

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. It doesn't mention prerequisites, context (e.g., for troubleshooting or setup), or comparisons to siblings like hana_show_env_vars or hana_describe_table. Without this, users must infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HatriGt/hana-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server