Skip to main content
Glama
Sign In
abap-config-mcp

abap-config-mcp

by netweaver1970
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Force Re-login

force_relogin
DestructiveIdempotent

Drop and re-establish this conversation's SAP ADT session when calls keep failing with HTTP 400 and automatic retry fails, releasing only this session's locks.

Instructions

Drop this conversation's SAP ADT session and log in again. Use when ADT calls keep failing with HTTP 400 (degraded stateful session) and the automatic retry has not recovered it. Releases this conversation's locks only — every conversation has its own SAP session.

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": "force_relogin"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectionIdNoSAP system connection ID (uses first if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.16.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's job is to explain blast radius, which it does well: locks released are limited to this conversation and each conversation has its own SAP session. It stops short of saying what happens to in-flight calls or uncommitted work at the moment the session is dropped.

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?

Two sentences, action first and usage condition second, with zero filler. The scoping caveat lands immediately after the action it constrains.

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 one-parameter recovery action with no output schema and annotations covering destructiveness, the definition supplies the essentials: trigger condition, retry precondition, and session scoping. Minor gaps are the fate of uncommitted work and whether the agent must re-run prior calls after re-login.

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 description coverage is 100% for the single connectionId parameter, so the schema carries the semantics and a baseline of 3 applies. The description never mentions connectionId, and its 'this conversation's session' framing sits slightly at odds with a selectable connection ID without clarifying how the two relate.

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 gives a specific verb and resource — drop this conversation's SAP ADT session and log in again — and pins the scope to a single conversation. No other sibling tool performs session recovery, so an agent can distinguish it 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 Guidelines4/5

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

It names the exact trigger (persistent HTTP 400 from a degraded stateful session) and adds a gate: only after automatic retry has failed. That implicitly rules out preemptive use, but there is no explicit 'do not use when' phrasing or named alternative recovery path.

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