Discovers ABAP Development Tools (ADT) services and endpoints to enable communication between ABAP systems and MCP clients.
Performs ADT discovery.
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": "adtDiscovery"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations and no output schema, the description carries the full burden of behavioral disclosure, yet reveals nothing about side effects, safety, or the nature of the discovery. It is a vague placeholder that offers no insight into what the tool actually does.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
While the description is only one sentence, it is under-specified rather than concise. It conveys almost no meaningful information and is closer to an empty placeholder, earning a 2 rather than a higher score.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is entirely inadequate given the lack of annotations, output schema, and parameter details. It fails to explain what ADT discovery means, what the tool returns, or how it relates to sibling discovery tools, leaving the agent without any basis for proper selection or invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema is empty with zero parameters, so there are no parameter semantics to document. The baseline of 4 applies because with 0 parameters, the description does not need to clarify any inputs; the empty schema already conveys the absence of parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is a tautology: it simply restates the tool name ('Performs ADT discovery') without any specific verb, resource, or scope. It does not distinguish itself from sibling tools like adtCoreDiscovery, making it impossible to understand what unique purpose it serves.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool, what situations call for it, or how it differs from alternatives such as adtCoreDiscovery. There is no mention of prerequisites, exclusions, or context of use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.