Skip to main content
Glama
Hollway

mcp-abap-abap-adt-api

by Hollway
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

whereUsedMethod

Read-only

Find all callers of an ABAP method in SAP systems. Identifies usage locations with optional source snippets to trace dependencies and assess impact.

Instructions

Who calls this method. usageReferences needs the line and column of the name inside the source, which means reading the class first and counting characters; here the method name is enough. Returns the callers with the object they sit in, and their source snippets with snippets=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodYesMethod name, e.g. CHECK_PLAN. The declaration is preferred over the implementation, because ADT answers a where-used on the declaration with every caller.
snippetsNoAlso fetch the source snippet of each usage (one more backend call, much larger answer).
classNameNoClass holding the method, e.g. ZCL_APP_PCK_PLAN.
interfaceNameNoInterface holding the method, for an interface method.
objectSourceUrlNoSource URL instead of a name, e.g. /sap/bc/adt/oo/classes/zcl_app/source/main.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is known. The description adds that it returns callers with their containing object and optionally source snippets, and highlights the simpler input requirement compared to usageReferences. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core purpose, and no redundant phrasing. Efficiently conveys the key contrast and output behavior.

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?

Given the tool is a read-only lookup with a well-documented schema, the description covers the essential behavioral difference (vs usageReferences) and the optional snippets behavior. It doesn't explain every parameter, but the schema handles that, so it is sufficiently complete.

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%, so all parameters are already documented. The description does not add additional semantic information about parameters beyond what the schema provides, so a baseline of 3 is appropriate.

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 clearly that it finds callers of a method, and differentiates from usageReferences by noting it only needs the method name rather than line/column coordinates. This is a specific verb+resource with sibling differentiation.

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 contrasts with usageReferences, explaining that usageReferences requires line/column coordinates, while this tool works with just the method name. This gives clear when-to-use guidance and implies the alternative.

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