Skip to main content
Glama

Search Function Modules

search_function_modules
Read-only

Find SAP function modules by name, description, or parameter across IS-U and FI-CA catalogs. Returns relevance-scored matches for a search query.

Instructions

Search for SAP function modules by name, description, or parameter. Use this when the user asks things like:

  • 'What FM reads installation data?'

  • 'Find function modules for Anlage'

  • 'Which FMs work with business partners?'

  • 'Show me FKK function modules'

The catalog contains IS-U and FI-CA function modules. Returns matching FMs with relevance scores.

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": {
      "query": "<query>"
    },
    "name": "search_function_modules"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return (default 10, max 50)
queryYesSearch query - can be a FM name (e.g., 'BAPI_USER_GET_DETAIL'), partial name (e.g., 'FKK_'), description keywords (e.g., 'installation', 'Anlage'), or parameter name/type (e.g., 'VKONT', 'partner')
include_paramsNoAlso search within parameter names, descriptions, and reference types (default True)

Output Schema

NameRequiredDescriptionDefault
hintNoGuidance when no results
queryYesThe search query used
resultsYesMatching function modules
successNo
total_resultsYesNumber of results found
total_in_catalogYesTotal FMs in catalog

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnlyHint and openWorldHint, and the description adds real value on top: the catalog is scoped to IS-U and FI-CA function modules only, and results come back ranked by relevance score. Missing pagination or limit behavior, but the output schema exists to carry return shape.

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?

Purpose and invocation triggers are front-loaded before the example bullets, and the catalog/return note closes it cleanly. Four bullets is slightly more than needed, but each illustrates a distinct query style (description, German term, domain, prefix).

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, fully-described, single-required-param search with an output schema, the description supplies the two things structured fields cannot: catalog scope and ranked-result behavior. Only explicit exclusions or limit interaction are absent.

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 query, limit, and include_params are already fully documented. The description's mention of parameter search loosely maps to include_params but adds no format, syntax, or wildcard detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search for SAP function modules') plus the three search axes (name, description, parameter), which separates it from search_classes/search_tables/search_transactions by resource type. It stops short of naming a sibling to route against, so it lands at clear-but-not-differentiated.

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?

The four sample user questions ('What FM reads installation data?', 'Show me FKK function modules') give concrete triggers for invoking this tool. There is no explicit when-not guidance, e.g. that lookups by exact technical name belong elsewhere or when to prefer search_tables.

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