Skip to main content
Glama

dumps

Retrieve and filter ABAP runtime dumps from SAP systems via ADT, with optional connection override.

Instructions

Retrieves a list of dumps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoAn optional query string to filter the dumps.
connectionNoOptional: SAP connection name to use for THIS call only (overrides the active connection; see listConnections). Immune to server restarts and concurrent switches.
Behavior2/5

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

The description does not disclose any behavioral traits such as side effects, authorization requirements, or performance implications. Without annotations, the description carries the full burden, but it only states the basic action.

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

Conciseness3/5

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

The description is very concise (one sentence), but it is too brief to be informative. It lacks structure and context, making it minimally acceptable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema and no annotations, yet the description fails to explain what 'dumps' are, what the returned list contains, or any filtering behavior. Essential context is missing for an agent to use it correctly.

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%, so the input schema already documents both parameters. The description adds no additional meaning beyond the schema, meeting the baseline expectation.

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?

The description clearly states the tool retrieves a list of dumps, with a specific verb and resource. No sibling tool directly overlaps, so differentiation is not needed, but the description could be more precise about the type of dumps.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description lacks any usage direction.

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