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

abap-config-mcp

by netweaver1970
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Connected Systems

connected_systems
Read-onlyIdempotent

Lists configured SAP system connections—IDs, URLs, users, clients, and the default—so you can select the correct connectionId for other tools.

Instructions

List the SAP systems this server is configured for: connection id, URL, user and client, with the default connection marked. Call this first when more than one system is configured, and pass the id as connectionId to any other tool. SOAP RFC connections are flagged as read-only (tables and sources only, no ADT). Only reads local configuration; does not contact SAP or log in.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.16.0

TDQS

A4.7/5.0
Behavior5/5

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

Adds real behavior beyond the annotations: it discloses that SOAP RFC connections are flagged and limited to tables and sources (no ADT), and that the call only reads local configuration without contacting SAP or logging in. That last clause is important context for an agent that would otherwise assume a network round-trip, and the read-only/network-free framing is consistent with readOnlyHint and idempotentHint.

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 sentences, front-loaded with what is returned before the usage instruction and the caveats. Every clause carries distinct information: output fields, sequencing rule, SOAP RFC limitation, and no-network guarantee. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by naming the returned fields, so an agent knows what it will get back. Combined with the no-login/no-network guarantee and the read-only SOAP RFC caveat, nothing material is missing for a zero-argument inventory 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?

Zero parameters, so the schema carries nothing to clarify; baseline is 4. The description still earns its keep by explaining the semantic role of the returned id (the connectionId argument accepted by every other tool), which is parameter meaning that no schema in this definition expresses.

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 SAP systems this server is configured for') and enumerates the returned fields (connection id, URL, user, client, default marker). An agent can tell immediately that this is a configuration-inventory tool, not an SAP-contacting operation like the ADT/ABAP siblings.

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 an explicit trigger ('Call this first when more than one system is configured') plus the follow-on action ('pass the id as connectionId to any other tool'), which is exactly the routing guidance an agent needs. It stops short of naming a when-not case or an alternative tool for single-system setups, so it misses the top tier.

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