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

abap-config-mcp

by netweaver1970
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Database Tables

search_database_tables
Read-onlyIdempotent

Find SAP database tables and views by keyword when the technical name is unknown, returning name, package, and description to guide field lookup and data queries.

Instructions

Find database tables and views by keyword when you do not know the technical name, via the ADT object search for types TABL and VIEW. Returns kind, name, package and description per hit, sorted by name, for standard, industry and Z/Y objects alike. Follow with describe_database_table for the fields, then read_table_contents or execute_data_query for the rows; use search_abap_objects for other object types. Read-only; maxResults applies to tables and views separately.

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": {
      "keyword": "<keyword>"
    },
    "name": "search_database_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesSearch text or name pattern; * is the wildcard (e.g. material*, *valuation*, T001*)
maxResultsNoMaximum results per object type (default: 50)
connectionIdNoSAP system connection ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.2
    • changedInput schema / properties / keyword / description
      Previous value: -"Description keyword to search for (e.g. 'article listing', 'transport request', 'material valuation')"New value: +"Search text or name pattern; * is the wildcard (e.g. material*, *valuation*, T001*)"
  2. First observedv1.16.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly/openWorld/idempotent, and the description still adds real value: the per-hit return shape (kind, name, package, description), name sorting, coverage of standard/industry/Z/Y objects, and the fact that maxResults is applied per object type rather than as a global cap.

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?

Three tightly packed sentences: purpose and scope first, then returns, then the follow-up chain and the sibling alternative. No filler and nothing important is buried at the end.

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 helpfully enumerates the returned fields and ordering, and it explains what maxResults does. Minor gaps remain (whether results are paged or capped by connection behavior), but an agent has enough to call it 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 keyword, maxResults and connectionId are already documented with wildcard examples and defaults. The description only reinforces the per-type maxResults behavior, which the schema already states, so it adds little beyond baseline.

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 ("Find database tables and views by keyword") and pins down the underlying mechanism (ADT object search for types TABL and VIEW), which cleanly separates it from search_abap_objects and describe_database_table.

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 frames the use case ("when you do not know the technical name"), names the follow-up tools in order (describe_database_table for fields, then read_table_contents or execute_data_query for rows), and routes other object types to search_abap_objects.

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