Skip to main content
Glama
Sign In
abap-config-mcp

abap-config-mcp

by netweaver1970
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

HANA Memory Report

hana_memory_report
Read-onlyIdempotent

Diagnose HANA memory pressure via read-only reports on host RAM/swap, service usage, top heap allocators, largest column tables, row store, SQL plan cache, and allocation limit before resizing.

Instructions

Diagnose HANA memory pressure on the tenant this ABAP system runs on, via the Customizing Engine's SICF endpoint (ADBC over SYS.M_* monitoring views — read-only). Reports host RAM/swap, per-service usage, top heap allocators, the largest loaded column tables, row store, SQL plan cache, and the configured global_allocation_limit. Use when the system is slow/swapping or before resizing. Needs engine v0.9.8+ (run customizing_engine_bootstrap to update).

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

Input Schema

NameRequiredDescriptionDefault
icfPathNoSICF path of the engine (default: /sap/bc/zmcp_cust)
connectionIdNoSAP system connection ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.16.0

TDQS

A3.9/5.0
Behavior4/5

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

Adds context beyond the annotations: the read-only claim is reinforced with the mechanism (ADBC over SYS.M_* monitoring views) and the operation is disclosed as an infrastructure dependency requiring engine v0.9.8+, with the bootstrap tool named as the fix. Open-world reach via the SICF endpoint is implied by the description and consistent with openWorldHint=true.

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?

Two sentences, front-loaded with the action and its target, then the evidence it returns and the prerequisite. The metric enumeration is long but each item tells the agent what diagnostic value to expect, so it mostly earns its space.

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?

With no output schema, the description compensates by enumerating the report contents (host RAM/swap, per-service usage, top heap allocators, column tables, row store, SQL plan cache, global_allocation_limit). The engine-version prerequisite and remediation are covered, leaving little an agent would need before invoking it.

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 both parameters are documented. The description only indirectly touches them (the SICF endpoint corresponds to icfPath, 'this ABAP system' to connectionId) without adding format or default guidance beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Diagnose HANA memory pressure on the tenant this ABAP system runs on') plus the transport (SICF endpoint, ADBC over SYS.M_* views) and the exact metric families returned. An agent can distinguish this from the ABAP-side counterpart by the HANA naming, though no sibling is named explicitly to contrast with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete trigger ('Use when the system is slow/swapping or before resizing') and an explicit remediation path when the prerequisite is unmet ('Needs engine v0.9.8+ (run customizing_engine_bootstrap to update)'). It does not state when *not* to use this versus the ABAP memory tool.

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