Skip to main content
Glama
rewe-mcp

rewe-mcp

by Robert-SD

Check REWE OAuth & mTLS Certificate Status

rewe_auth_status
Read-only

Inspect REWE SSO session status, token expiry, mTLS client certificate configuration, and default market to verify authentication and market selection.

Instructions

Inspect current REWE Keycloak SSO session status (token source, expiry, customerId), Cloudflare mTLS client certificate configuration, and active default market selection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
messageNo
savedAtNo
expiresAtNo
customerIdNo
mtlsSourceYes
tokensFileYes
mtlsKeyPathNo
tokenSourceYes
marketConfigYes
mtlsCertPathNo
authenticatedYes
hasAccessTokenYes
mtlsConfiguredYes
hasRefreshTokenYes
expiresInSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description then adds real value by listing exactly which signals are inspected (token source, expiry, customerId, certificate config, default market), which tells the agent this is a pure diagnostic read. It stops short of describing failure/expiry states or what happens with no session, which would have pushed it higher.

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?

A single front-loaded sentence: the verb and scope come first, followed by the three inspection targets. Every clause carries new information, with no preamble or repetition.

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?

With an output schema supplied, the description need only convey what the tool covers and that it is a side-effect-free read. It covers all three domains the title implies (OAuth session, mTLS certificate, market selection), and there are no parameters to document, so nothing an agent needs to call it correctly is missing.

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?

The tool takes zero parameters, so there is no parameter semantics to add and the baseline of 4 arguably applies; however the description's parenthetical field list is about returned data rather than inputs, so I hold it at a comfortable baseline rather than awarding extra credit.

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 names a specific verb (Inspect) plus three concrete resources: Keycloak SSO session status, Cloudflare mTLS certificate configuration, and default market selection, and even enumerates the session fields (token source, expiry, customerId). No sibling touches auth/certificate diagnostics, so an agent can immediately separate this from the data-fetching tools.

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

Usage Guidelines3/5

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

Usage is only implied: the word 'current' plus the diagnostic framing suggests calling it to verify session or certificate health before other REWE calls, but the description never states when to call it, when not to, or what to do if it reports an unauthenticated state. No alternative or prerequisite is named.

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