Skip to main content
Glama

Sap Spro Search

sap_spro_search
Read-only

Search SAP IMG customizing activities by keyword to locate where configuration is maintained, returning matching activities with parent node and area for navigation via SM30 or related transactions.

Instructions

Search the SAP Implementation Guide (IMG) for customizing activities by keyword. USE THIS to find where specific SAP configuration is maintained (e.g., 'country', 'pricing', 'tax'). Returns matching IMG activities with their parent node and area. The WebGUI search covers all IMG text content; the desktop search only the top two levels of the IMG tree (the result's scope_note says so). Results can then be used to navigate to specific configuration via SM30 or other transactions.

Note: First search in a language may be slow (30-60s) while the text index is built. Subsequent searches are faster.

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

Input Schema

NameRequiredDescriptionDefault
queryYesSearch keyword (e.g., 'country', 'pricing', 'tax')
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.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses substantial behavior: the difference in coverage between WebGUI and desktop search, that scope_note in the result signals which was used, and the first-search 30-60s index-build latency. This is exactly the operational context annotations cannot convey.

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?

Front-loaded with purpose, then usage cue, then the WebGUI/desktop distinction, and finishes with the latency note. Every sentence carries information, though the parenthetical about scope_note is slightly nested and verbose.

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?

For a read-only search tool with an output schema and full parameter coverage, the description supplies everything else an agent needs: what it searches, coverage differences between modes, and a first-call latency warning so the agent does not time out.

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 four parameters are already documented, and the description adds no meaning to query, session, agent_id, or output_file. Baseline 3 applies when the schema carries the parameter burden.

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?

The description uses a specific verb and resource ('Search the SAP Implementation Guide (IMG) for customizing activities by keyword') and gives concrete example keywords like 'country', 'pricing', 'tax'. The IMG resource is unambiguous against siblings such as search_tables or search_transactions, though no sibling is named explicitly.

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?

It states 'USE THIS to find where specific SAP configuration is maintained' and describes the follow-up workflow (navigate to configuration via SM30 or other transactions). There is no explicit when-not-to-use guidance or named alternative, which keeps it below 5.

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