Skip to main content
Glama
Freight-Art

abapsmith

by Freight-Art
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Read IMG customizing catalog

abap_img
Read-only

Search SAP IMG activities by query. Show paths, objects, tables, tree children, and DDIC fields for customizing objects.

Instructions

Read the IMG customizing catalog: search (query) finds activities; show (activity) returns its path, objects and tables; tree (node/treeId optional) lists a node's children; objects (object, kind optional) returns a customizing object's DDIC tables and fields. search/tree page via after/limit (default 25, ceiling 200) — pass back the exact {"after": ""} a response gives; there is no numeric offset. Fields not valid for the mode are rejected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoobjects only: a hint for the object's kind, used when the name is ambiguous.
modeYessearch: find activities by title/id text. show: an activity's reference-IMG path, objects and tables. tree: a node's reference-IMG children. objects: an object's DDIC tables and fields.
nodeNotree only: the node to list children of. Omit for that tree's own root.
afterNosearch/tree only: opaque keyset cursor copied from a previous response's paging note. Omit for the first page.
limitNosearch/tree only: max rows to return. Default 25, ceiling 200.
queryNosearch only: a term with no "*" matches as a substring; "*" is an explicit wildcard, "*" alone matches everything.
objectNoobjects only: a view, view cluster, table, or customizing object name.
treeIdNotree only: the tree a node id belongs to, echoed back as treeId on a previous tree response (e.g. after following a REF node). Omit to use the reference-IMG tree.
activityNoshow only: the IMG activity id to display.
languageNoSingle-character SAP language key (SPRAS), e.g. E or D — not EN/DE. Defaults to the server's configured language, else E.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.25
    • changedInput schema / properties / language / description
      Previous value: -"single-character SAP language key (SPRAS), e.g. \"E\" for English, \"D\" for German — not a 2-letter ISO code. Defaults to the server's configured language, else \"E\"."New value: +"Single-character SAP language key (SPRAS), e.g. E or D — not EN/DE. Defaults to the server's configured language, else E."
    • changedInput schema / properties / mode / description
      Previous value: -"search: find activities by title/id text. show: one activity's reference-IMG path, maintenance objects and tables. tree: the reference-IMG node children under a node. objects: a view/cluster/table/customizing object's underlying DDIC tables and fields."New value: +"search: find activities by title/id text. show: an activity's reference-IMG path, objects and tables. tree: a node's reference-IMG children. objects: an object's DDIC tables and fields."
    • changedInput schema / properties / query / description
      Previous value: -"search only: a term with no \"*\" matches as a substring of the title or id; \"*\" is an explicit wildcard, and \"*\" alone matches everything."New value: +"search only: a term with no \"*\" matches as a substring; \"*\" is an explicit wildcard, \"*\" alone matches everything."
    • changedInput schema / properties / treeId / description
      Previous value: -"tree only: the tree a node id belongs to (echoed back as treeId on a previous tree response, e.g. after following a REF node into a different tree). Omit to use the reference-IMG tree."New value: +"tree only: the tree a node id belongs to, echoed back as treeId on a previous tree response (e.g. after following a REF node). Omit to use the reference-IMG tree."
  2. Addedv0.4.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark readOnlyHint and openWorldHint, but the description adds substantial behavioral details: paging via opaque cursor with no numeric offset, exact cursor format to pass back, default/ceiling limits, and mode-specific field rejection. This goes well beyond the structured annotations.

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?

The description is compact and front-loaded, starting with the overall purpose, then briefly enumerating modes and key constraints. Every sentence contributes; the paging and validation rules are stated succinctly without redundancy.

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 tool with 10 parameters and 4 modes, the description covers all modes, parameter applicability, paging, and validation. It does not detail response structures or error behavior, but given the read-only annotations and the lack of an output schema, the core call semantics are complete enough.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Beyond the 100% schema coverage, the description maps each parameter to its mode (query→search, activity→show, node/treeId→tree, object/kind→objects) and explains paging semantics, wildcard behavior, language key format, and field rejection rules—all adding meaning not obvious from the schema alone.

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?

The description clearly states 'Read the IMG customizing catalog' and enumerates four distinct modes (search/show/tree/objects), each with a specific verb and resource. It differentiates from sibling abap_img_edit, which presumably modifies the catalog, making the read-only purpose clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description explains what each mode does and which parameters apply to which mode, giving clear context for selecting the right mode. However, it does not explicitly mention when to prefer this tool over siblings like abap_img_edit or abap_read, nor does it provide when-not-to-use guidance.

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

Deploy Server

Other Tools