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

abap-config-mcp

by netweaver1970
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Read Customizing Data

customizing_read
Read-onlyIdempotent

Read current rows from a customizing table or maintenance view as an aligned text table, optionally filtering by one key field to isolate the relevant configuration records.

Instructions

Read the current rows of a customizing table or maintenance view (a view is resolved to its base table) as an aligned text table, optionally filtered to rows where one key field equals one value. The filter applies only when both keyField and keyValue are given. Use customizing_diff to compare two org units, customizing_describe for the field list, and read_table_contents for non-customizing tables. Read-only; needs table read authorization (S_TABU_DIS); returns at most maxRows rows.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "objectName": "<objectName>"
    },
    "name": "customizing_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxRowsNoMaximum rows to return (default: 100)
keyFieldNoField to filter on, compared for equality (e.g. WERKS, BUKRS); used only together with keyValue
keyValueNoValue the field must equal, as stored (e.g. '0001'); used only together with keyField
objectNameYesMaintenance view or table name (e.g. V_T001W, T001W, TCURR)
connectionIdNoSAP system connection ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.16.2
    • changedInput schema / properties / keyField / description
      Previous value: -"Key field to filter on (e.g. WERKS, BUKRS, VKORG)"New value: +"Field to filter on, compared for equality (e.g. WERKS, BUKRS); used only together with keyValue"
    • changedInput schema / properties / keyValue / description
      Previous value: -"Value to filter for (e.g. '1000', 'DE01')"New value: +"Value the field must equal, as stored (e.g. '0001'); used only together with keyField"
    • changedInput schema / properties / objectName / description
      Previous value: -"Maintenance view or table name (e.g. V_T001W, T001, TVKO)"New value: +"Maintenance view or table name (e.g. V_T001W, T001W, TCURR)"
  2. First observedv1.16.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is given. The description still adds real context the annotations cannot carry: view-to-base-table resolution, the S_TABU_DIS authorization requirement, and the maxRows row cap. It stops short of describing column ordering or behavior on an unknown table name, so it is a strong 4 rather than a 5.

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?

Four dense sentences, front-loaded with the core action, then the filter rule, then sibling routing, then authorization and limits. No redundant or filler wording.

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?

There is no output schema, so the description must convey the return shape — it does ("aligned text table", capped at maxRows). Connection selection via connectionId is only implied by noting SCH_TABU_DIS auth and a connection-less framing, a minor gap for a multi-system tool.

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?

Schema coverage is 100%, so each parameter is already documented; baseline is 3. The description adds the joint condition that the filter applies only when both keyField and keyValue are supplied, plus the concrete effect of maxRows, which is modest but genuine added meaning.

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?

States a specific verb and resource ("Read the current rows of a customizing table or maintenance view") and adds a distinguishing behavioral detail — views resolve to their base table — that separates it from plain table reads.

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

Usage Guidelines5/5

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

Explicitly routes the agent to alternatives with the conditions that select them: customizing_diff for comparing two org units, customizing_describe for field lists, read_table_contents for non-customizing tables. Nothing is left to inference.

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