Skip to main content
Glama
Sign In
OpenAPI MCP Gateway

OpenAPI MCP Gateway

by mroops0111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Logs out current logged in user session.

logout_user
Read-onlyIdempotent

Terminates the active user session and revokes authentication, logging the user out of the system.

Instructions

Log user out of the system.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.2
    • removedInput schema / title
      Removed value: -"upstream_callableArguments"
  2. First observedv1.0.0

TDQS

B3.3/5.0
Behavior1/5

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

Annotation Contradiction: The description states 'Log user out of the system,' which is a state-changing operation, but annotations include readOnlyHint: true, meaning the tool is marked as not modifying state. This is a direct contradiction, and no additional behavioral context is provided.

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?

The description is a single, front-loaded sentence that conveys the action without unnecessary words or repetition. It is concise and appropriately sized for such a simple tool.

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

Completeness3/5

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

Given the zero-parameter schema and simple action, the description is nearly sufficient, but it lacks context about session invalidation or post-condition behavior. The annotation contradiction further undermines the reliability of the tool's behavioral profile, making it a minimum-viable but incomplete description.

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 and the schema is empty, so there are no parameter meanings to clarify. Baseline 4 is appropriate since no description is needed for absent parameters.

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 uses a specific verb ('log out') and identifies the target ('the system'), clearly distinguishing it from sibling tools like login_user or update_user. The title further clarifies that it targets the current logged-in user session.

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

Usage Guidelines2/5

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

No usage guidance is provided. The description does not state when to use this tool, prerequisites (e.g., must be logged in), or alternatives, leaving the agent to infer context from the name and title alone.

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