OpenAPI MCP Gateway

Logs user into the system.

login_user

Read-onlyIdempotent

Authenticate users with their username and password to grant access to the system.

Instructions

Log into 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": "login_user"
  }
}

Input Schema

Name	Required	Description	Default
`password`	No	The password for login in clear text
`username`	No	The user name for login

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.6.2Aug 11, 2026
- removedInput schema / properties / password / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / password / default
```
Removed value: -null
```
- removedInput schema / properties / password / title
```
Removed value: -"Password"
```
- addedInput schema / properties / password / type
```
Added value: +"string"
```
- removedInput schema / properties / username / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / username / default
```
Removed value: -null
```
- removedInput schema / properties / username / title
```
Removed value: -"Username"
```
- addedInput schema / properties / username / type
```
Added value: +"string"
```
- removedInput schema / title
```
Removed value: -"upstream_callableArguments"
```
First observedv1.0.0Jun 11, 2026

TDQS

C2.4/5.0

Behavior1/5

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

The description directly contradicts the annotations: readOnlyHint is true, but 'Log into the system' implies a session-creating side effect. No behavioral details (e.g., token return, session expiry) are disclosed beyond the misleading annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief and does not waste words, but it is under-specified to the point of adding nothing beyond the title. It is concise but not meaningfully structured or informative.

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

Completeness2/5

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

Given the absence of an output schema and the simple parameter set, the description should still explain expected behavior or return value. It fails to mention success/failure outcomes, session details, or the effect of invalid credentials, making it incomplete for a login action.

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 input schema already provides full descriptions for both username and password (100% coverage). The description adds no additional parameter semantics, so it meets the baseline for schema-documented parameters.

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?

The description 'Log into the system' clearly states the action and resource, distinguishing it from siblings like get_user_by_name or update_user. However, it is virtually identical to the name and title, adding no new specificity, so it does not earn a 5.

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

Usage Guidelines1/5

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

The description offers no guidance on when to use this tool versus alternatives (e.g., get_user_by_name for fetching user info), nor any prerequisites like the user existing or session handling. It is entirely absent of usage context.

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