Skip to main content
Glama

logoutUser

Read-onlyIdempotent

Ends the current user session to securely terminate access and prevent unauthorized use.

Instructions

Logs out current logged in user 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": "logoutUser"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

The description restates the tool name and adds no behavioral context beyond it: it does not say whether the server-side token/session is invalidated, whether the call succeeds when no session exists, or what the caller receives. Worse, the claim of ending a session is a state change, which sits awkwardly against readOnlyHint=true in the annotations.

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?

A single short sentence with no filler, front-loading the action. It is efficient but borders on under-specification rather than trimming genuine redundancy.

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?

For a zero-parameter session tool the bar is low, and annotations already carry the safety profile, so the description is close to adequate. Still missing are the post-call session state and the failure mode when no session is active, both of which an agent would want before calling it in a flow.

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 takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies the target is the caller's own implicit session rather than an arbitrary user id.

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?

States a specific verb and resource: terminating the current logged-in user's session. It is unambiguous on its own, though it never contrasts itself with the sibling loginUser or explains the scope of what 'logout' entails server-side.

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 implied rather than stated: an agent infers it should call this to end a session. There is no guidance on prerequisites (does a session have to exist?), what to do if no user is logged in, or when a caller should prefer this over simply discarding credentials.

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