Skip to main content
Glama

Sap Get Capabilities

sap_get_capabilities

Retrieves every available SAP session tool and its full description so agents can identify capabilities and choose correct actions before starting work.

Instructions

RECOMMENDED: Call at the start of every SAP session. Returns all available tools with their full descriptions. Reading this first helps you understand what capabilities are available, work faster, and avoid common mistakes like clicking buttons when keyboard shortcuts are available.

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_get_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
errorNoError message if success=False
popupNoPresent when a popup dialog is active on screen
toolsNoAll available tools with their names and descriptions
successNoWhether the operation succeeded
active_windowNoWhich window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open.
sap_knowledgeNoFree-form SAP domain knowledge, tips, and best practices in markdown format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description has to carry the full behavioral burden itself. It discloses the return content ('all available tools with their full descriptions') and the practical effect of calling it ('work faster, avoid common mistakes'), though it does not say how large the response is, whether it is cached, or that it is a pure read operation.

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 three sentences and leads with the recommendation, followed by the return value, then the rationale. The final clause about 'clicking buttons when keyboard shortcuts are available' is slightly promotional and could be trimmed, but overall the structure is tight and the ordering puts what matters first.

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?

For a zero-parameter discovery tool with an output schema plus full schema description coverage, the description covers everything an agent needs: what it returns, when to call it, and why. Because return values are documented by the output schema, leaving out a detailed response format is appropriate rather than a gap here.

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?

The tool has zero parameters, so there is nothing to disambiguate, and the default baseline of 4 applies. The description correctly implies parameterless invocation by never referencing any input.

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 action and result: it 'Returns all available tools with their full descriptions.' That verb+resource pairing makes it immediately distinguishable from the sibling tools, which all act on SAP screens, tables, or repositories rather than on the tool catalog itself.

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?

The timing guidance is explicit and front-loaded: 'Call at the start of every SAP session.' It does not cover when not to call the tool or name alternative discovery paths, so the agent must infer that a single call per session is enough, but it still gives clear usage context.

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