Skip to main content
Glama

Sap Se11 Lookup

sap_se11_lookup
Read-only

Retrieve live ABAP Dictionary metadata for tables or structures, including field names, data types, lengths, and descriptions, as structured data instead of running the SE11 transaction.

Instructions

Look up table or structure metadata from SE11 (ABAP Dictionary). If sap-adt is available, prefer its get_table_fields or get_object_info tools. USE THIS instead of sap_transaction('SE11') - faster and returns structured data. Returns field names, data types, lengths, and descriptions. Supports single name or list of names. Always queries live from SAP. Use object_type='table' for database tables, 'structure' for data structures. For large requests (>10 objects), provide output_file to write results to JSON file instead of returning inline (avoids context overflow).

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": {
      "names": "<names>",
      "object_type": "<object_type>"
    },
    "name": "sap_se11_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYesSingle name or list of table/structure names
sessionNoSession ID (e.g., "s1", "s2"). None uses primary session.
agent_idNoAgent identifier for binding check. Optional.
object_typeYes'table' for database tables, 'structure' for structures
output_fileNoIf provided, write full results to this JSON file and return summary. Recommended for >10 objects to avoid context overflow.

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, and the description adds genuinely new context: results are always queried live from SAP, the payload contains field names/types/lengths/descriptions, and large requests write to a JSON file to avoid context overflow. It stops short of describing failure modes, permissions, or session-binding behavior, which leaves a minor gap for a live-query tool.

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 routing, then return shape, then batch guidance — a logical order with no filler sentences. It loses a point for duplicating the object_type and output_file explanations that already appear in the schema, which is mild redundancy rather than bloat.

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?

With an output schema present, return values needn't be spelled out, and the description still summarizes the key returned fields plus the file-vs-inline behavior. Combined with the sibling routing and the >10 object threshold, an agent has nearly everything needed to invoke it correctly; only error/permission behavior is 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 description coverage is 100%, so names, session, agent_id, object_type and output_file are already documented, including the >10 objects recommendation that the description repeats. The description's only added value is restating the enum semantics and the single-name-or-list flexibility, which the schema already provides; baseline 3 is appropriate.

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 table or structure metadata from SE11 (ABAP Dictionary)') and names the exact sibling it substitutes for (sap_transaction('SE11')). An agent can distinguish it from the other sap_seXX_lookup tools because the resource is explicitly ABAP Dictionary tables/structures.

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 explicit routing: prefer sap-adt get_table_fields/get_object_info when available, use this instead of sap_transaction('SE11'), and choose object_type='table' vs 'structure'. It also names the threshold condition (>10 objects) that selects the output_file path, so the when/when-not decision is fully specified.

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