Skip to main content
Glama

getObjectSource

Read ABAP source from an ADT URL. For large objects, use search with context or specify a line range to avoid truncation.

Instructions

Reads ABAP source. For LARGE objects do NOT read it whole: use search (grep with line numbers + context) to locate statements, or startLine/endLine to read a window. Without those, a very large source is truncated (head only) with totalLines and a hint. Line numbers in the output are display-only — do not include the "NNN: " prefix in editObjectSource.oldString.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoReturn only lines matching this text/regex, with line numbers and context. Ideal to locate a statement (e.g. "FROM ckmlpp").
endLineNoLast line to return (1-based) when reading a window.
optionsNoOptional ObjectSourceOptions (e.g. version).
maxCharsNoTruncation guard for full reads (default 45000).
startLineNoFirst line to return (1-based) when reading a window.
connectionNoOptional: SAP connection name to use for THIS call only (overrides the active connection; see listConnections). Immune to server restarts and concurrent switches.
ignoreCaseNoCase-insensitive search (default true).
contextLinesNoLines of context around each search match (default 3, max 20).
objectSourceUrlYesADT source URL (e.g. .../programs/programs/ZFOO/source/main).
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses truncation behavior for large objects and warns that line numbers are display-only. Could mention read-only nature, but adds useful behavioral context.

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?

Exceptionally concise: two sentences covering purpose, warnings, and alternatives. Front-loaded with essential information; no wasted words.

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?

Given 9 parameters and no output schema, the description covers critical usage patterns (large objects, line number format) adequately. Schema handles parameter details, so description adds value without being exhaustive.

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 coverage is 100% with parameter descriptions. Description adds usage context (e.g., how to use search, startLine, endLine for large objects) but does not provide significant new meaning beyond the schema.

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?

Purpose is clearly stated as 'Reads ABAP source,' using a verb and resource. However, it does not explicitly distinguish from sibling tools like editObjectSource or searchObject, only from using the search parameter within the same tool.

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?

Provides explicit guidance for large objects: use search, startLine/endLine instead of reading whole source. Does not address when to use this tool versus sibling tools like searchObject, but gives clear within-tool alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rafaelssclaudio/MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server