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

abap-config-mcp

by netweaver1970
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ADT Discovery

adt_discovery
Read-onlyIdempotent

List the ADT services and collections an SAP system exposes. Use it to check whether a feature exists on the current release before calling a dependent tool, or when a tool fails with 404.

Instructions

List the ADT services the SAP system exposes, each with its collection titles or hrefs, from the ADT discovery document. Use it to check whether a feature (for example a data preview or ATC endpoint) exists on this release before relying on a tool that needs it, or when a tool fails with 404. Read-only; takes no object input and returns a plain list, which can be long.

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

Input Schema

NameRequiredDescriptionDefault
connectionIdNoSAP system connection ID (default connection if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.2
    • changedInput schema / properties / connectionId / description
      Previous value: -"SAP system connection ID"New value: +"SAP system connection ID (default connection if omitted)"
  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 declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered; the description still adds real value by saying it takes no object input and that the returned plain list 'can be long' — a payload-size warning an agent needs for context budgeting. It stops short of describing item shape in detail or ordering, which keeps it at 4 rather than 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?

Two sentences, front-loaded with what it returns, then when to call it, then behavioral caveats. Every clause carries information; nothing is repeated from the title or annotations except a brief read-only restatement that reinforces safety.

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?

For a zero-required-parameter, no-output-schema tool this covers purpose, triggers, input expectations and payload size. The only remaining gap is the exact structure of the returned list items, which an agent must discover on first call rather than reading here.

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% and the single connectionId parameter is fully documented in the schema, so the baseline is 3. The description's 'takes no object input' usefully confirms that no repository object selector exists, but adds no format or default detail beyond the schema.

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 — 'List the ADT services the SAP system exposes' — and names the source document (the ADT discovery document) plus the per-item payload ('collection titles or hrefs'). No sibling in the catalog performs discovery, and the description makes clear this is a capability-enumeration tool, not an object reader.

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?

Gives two concrete invocation triggers: pre-flight capability check before relying on a feature-dependent tool, and diagnosing a 404 failure. These are actionable conditions an agent can match against its situation without inferring anything from sibling names.

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