Skip to main content
Glama

Sap Se37 Lookup

sap_se37_lookup
Read-only

Look up function module signatures and metadata from SE37, including import/export/changing/tables parameters, exceptions, typing, defaults, and descriptions for one or multiple FMs.

Instructions

Look up function module metadata from SE37 (Function Builder). If sap-adt is available, prefer its get_source tool for reading FM source code. USE THIS instead of sap_transaction('SE37') - faster and returns structured data. Returns function module signature including import/export/changing/tables parameters and exceptions. Supports single FM or list of FMs. Each parameter includes: name, typing (LIKE/TYPE), reference type, default value, optional flag, and description.

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": {
      "function_modules": "<function_modules>"
    },
    "name": "sap_se37_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionNoSession ID (e.g., "s1", "s2"). None uses primary session.
agent_idNoAgent identifier for binding check. Optional.
output_fileNoIf provided, write full results to this JSON file and return summary. Recommended for >5 function modules to avoid context overflow.
function_modulesYesSingle FM name or list of names (e.g., 'RFC_READ_TABLE' or ['RFC_READ_TABLE', 'BAPI_USER_GET_DETAIL'])

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 and openWorldHint=false, so safety is covered; the description adds a comparative behavioral trait, that it is faster and returns structured data than the transaction route. It gives no note on error behavior for a non-existent FM name or on what the summary contains when output_file is used, which keeps it below a 5.

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?

The most decision-relevant content (what it does, sibling preference) is front-loaded, and sentences are short. The closing enumeration of per-parameter return fields (name, typing, LIKE/TYPE, default, etc.) is somewhat redundant given an output schema exists and could be trimmed.

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 read-only lookup with four well-documented parameters and a dedicated output schema, the description is nearly complete: it covers scope, alternatives, input shape, and output volume handling. The remaining gap is failure behavior for invalid or inaccessible function module names.

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 the baseline is 3. The description restates that a single FM name or a list is accepted and mentions the output_file threshold, but both points already appear in the schema descriptions, so it adds little new meaning.

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?

The description names a specific verb and resource ("Look up function module metadata from SE37") and immediately scopes what the result contains. It explicitly distinguishes itself from two siblings, sap_transaction('SE37') and sap-adt get_source, so an agent can pick it without opening other schemas.

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?

It gives an explicit preference rule ("USE THIS instead of sap_transaction('SE37')") and a conditional alternative (use sap-adt get_source when reading FM source code), which cleanly separates metadata lookup from source retrieval. Both the when-to-use and the not-for-this-case conditions are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.