Skip to main content
Glama

Search Transactions

search_transactions
Read-only

Search SAP transactions by code or description to identify the right t-code and module for tasks like creating sales orders or displaying customer master data.

Instructions

Search for SAP transactions by description or transaction code. Use this when the user asks things like:

  • 'How do I create a sales order?'

  • 'What transaction displays customer master?'

  • 'Show me material management transactions'

  • 'What is VA01?'

Returns matching transactions 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_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoOptional filter by SAP module area. Common values: - 'SD' = Sales & Distribution - 'MM' = Materials Management - 'FI' = Financial Accounting - 'CO' = Controlling - 'PP' = Production Planning - 'HR' = Human Resources - 'BC' = Basis/Technical
limitNoMaximum results to return (default 10, max 50)
queryYesSearch query - can be a transaction code (e.g., 'VA01'), partial code (e.g., 'VA'), or description keywords (e.g., 'create sales order', 'customer master')

Output Schema

NameRequiredDescriptionDefault
hintNoGuidance when no results
queryYesThe search query used
resultsYesMatching transactions
successNo
total_resultsYesNumber of results found (0 is valid)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only that results come back with relevance scores, and says nothing about ranking behaviour, empty/ambiguous matches, or result caps beyond what the schema's limit field already documents.

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-loads the one-line purpose before the example list, and the bullets earn their place by illustrating query shapes. The bulleted example block is slightly long for the amount of new information it carries, but nothing is redundant filler.

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?

An output schema exists and the input schema is fully described, so the description does not need to explain return fields or parameter formats. What remains adequate for a read-only search tool; only matching/ranking behaviour is left implicit.

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%, with query, area (including module-code values) and limit all documented inline, so the baseline is 3. The description's query examples ('VA01', 'VA', 'customer master') restate what the schema already provides rather than adding new semantics.

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 a specific verb and resource ('Search for SAP transactions') plus the two supported lookup modes (description keywords or transaction code). The resource is clearly distinct from sibling search tools such as search_tables, search_classes and search_function_modules, so an agent can route without opening any schema.

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?

Gives concrete user-intent triggers ('How do I create a sales order?', 'What is VA01?') that map natural-language questions onto this tool, which is strong when-to-use guidance. It stops short of stating when NOT to use it or naming the sibling search tools as alternatives for non-transaction objects.

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