Skip to main content
Glama

Sap Sm30 Lookup

sap_sm30_lookup
Read-only

Look up SAP SM30 maintenance view entries in read-only mode to get structured data with parsed columns instead of navigating the transaction manually.

Instructions

Look up SAP table maintenance view entries from SM30 (read-only display mode). USE THIS instead of sap_transaction('SM30') - faster and returns structured data. Returns entries from the maintenance view with dynamically-parsed columns. Supports any flat table view (e.g., V_T005 for countries, custom Z* views). Non-flat views (SM34/cluster/hierarchical) are detected and reported as unsupported. Note: only the first page of rows is returned (typically ~12 rows); views with more entries will report the total row_count from the view header.

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": {
      "view_name": "<view_name>"
    },
    "name": "sap_sm30_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionNoSession ID (e.g., "s1", "s2"). None uses primary session.
agent_idNoAgent identifier for binding check. Optional.
view_nameYesThe maintenance view or table name (e.g., 'V_T005', 'V_T002')
output_fileNoIf provided, write full results to this JSON file within the configured output directory (OUTPUT_DIR, default: current working directory) and return summary.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint it discloses real behavior: dynamically-parsed columns per view, explicit unsupported-view detection, and a hard pagination limit of roughly 12 rows with a total row_count available from the view header. That last point materially affects how the agent interprets results and is not derivable from annotations or schema.

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

Conciseness5/5

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

Front-loaded with the primary use instruction and the sibling comparison, then descending into view-type support and pagination caveats. Every sentence carries an actionable fact; there is no restatement of the tool name or filler.

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 single-required-parameter lookup with an output schema and read-only annotations, the description covers purpose, alternative, supported and unsupported inputs, and the one result-shape caveat (truncation plus row_count). Nothing an agent needs to call it correctly or interpret output is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 earns extra by constraining valid view_name values (flat maintenance views only, with V_T005/V_T002/Z* examples) and by noting the row-limit consequence. It does not add meaning for session/agent_id/output_file, which the schema already documents.

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 ("Look up SAP table maintenance view entries from SM30") and pins the mode (read-only display). It explicitly contrasts itself with sap_transaction('SM30'), so an agent can distinguish it from the most likely sibling 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit rule: use this INSTEAD of sap_transaction('SM30') because it is faster and returns structured data. It also defines the boundary of applicability (flat table views supported; SM34/cluster/hierarchical reported unsupported), which tells the agent when to stop using it.

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