Skip to main content
Glama

abapGit List Repositories

sap_abapgit_list_repos
Read-onlyIdempotent

List and filter registered abapGit repositories by name, package, URL, or key, returning metadata to identify the correct repo before calling a pull.

Instructions

List registered abapGit repositories with their metadata. Returns repo names, Git URLs, packages, branches, last pull timestamps and (when the report provides it) the repository key, plus total_count and matched_count. Use name/package/url/key to filter instead of listing everything (a system can have hundreds of repositories): name, package and url are case-insensitive substrings, or globs when they contain * or ?; key is an exact match, digits, zero-padded to 12; all given filters must match. compact=True returns only name, package and key. Use this to discover the correct repo name before calling sap_abapgit_pull.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sap_abapgit_list_repos"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoExact abapGit repository key (1-12 digits, zero-padded to 12; surrounding blanks are stripped). Optional.
urlNoSame, for the Git URL (never matches offline repositories). Optional.
nameNoCase-insensitive substring or glob (* and ?) for the repository name. Optional.
compactNoReturn only name, package and key per repository.
packageNoSame, for the ABAP package. Optional.
sessionNoSession ID (e.g., "s1", "s2"). None uses primary session.
agent_idNoAgent identifier for binding check. Optional.

Output Schema

NameRequiredDescriptionDefault
errorNoError message if success=False
popupNoPresent when a popup dialog is active on screen
reposNoRegistered repositories that match the filters (AbapGitRepoSummary entries when compact=True)
messageNoHint, e.g. when no repository matches the filters
successNoWhether the operation succeeded
total_countNoNumber of all registered repositories (before filtering); None when the list was not read
active_windowNoWhich window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open.
matched_countNoNumber of repositories that match the filters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare this as a safe, read-only, idempotent, closed-world operation, so the description does not need to restate safety. It adds useful behavior beyond annotations: the exact return payload, compact-mode projection, filter AND semantics, glob behavior, and the scale warning about hundreds of repositories. It stops short of explaining any ordering or pagination behavior, but no pagination parameters exist.

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?

The description is front-loaded with the operation and return payload, then follows with filtering guidance and the pull handoff. It is efficient overall, though it repeats several parameter behaviors that the schema already fully documents, which is the main redundancy.

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?

An output schema exists, so the description does not need to fully define response structure, but it still summarizes the returned fields and counts. With annotations covering safety and the schema covering parameter formats, the description supplies everything else an agent needs: filtering strategy, compact mode, scale context, and the next tool to call.

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 still adds meaningful semantics, especially that all given filters must match and that compact=True returns only name, package and key. Most other filter details are already in the schema, so it is useful but somewhat duplicative.

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 states a specific verb and resource: list registered abapGit repositories with metadata. It enumerates returned fields including total_count and matched_count, and explicitly names the downstream sibling sap_abapgit_pull, so an agent can distinguish it from other SAP tools without opening the 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?

It explicitly tells the agent to filter by name/package/url/key instead of listing everything, gives the reason (systems can have hundreds of repos), and routes discovery to the correct repo name before calling sap_abapgit_pull. That is explicit when-to-use guidance with a named alternative workflow.

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