Skip to main content
Glama

loginUser

Read-onlyIdempotent

Authenticates a user with a username and password to grant system access.

Instructions

Logs user 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": "loginUser"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordNoThe password for login in clear text
usernameNoThe user name for login

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the description adds nothing about behavior beyond that. It omits what an agent most needs to know here: whether credentials are returned (token/session id) and whether subsequent calls need to carry them. The server-side effect of starting a session sits in mild tension with readOnlyHint, though the description does not explicitly claim a write, so this is not a contradiction.

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?

A single short sentence with no wasted words, but its brevity comes from under-specification rather than efficiency. The one fact given is front-loaded but there is no structure for anything else.

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?

No output schema exists, so the description must explain what a successful login returns and how credentials are used downstream; it does neither. For an authentication entry-point tool with optional (0 required) parameters, the agent cannot tell whether both fields are truly needed or what happens on failure.

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%, with username and password each documented in the schema (password noted as clear text). The description adds no format, encoding, or credential-handling nuance beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Logs user into the system" essentially restates the tool name loginUser (verb + resource already encoded in the identifier) and adds no distinguishing detail. It does not say what a successful login produces (session, token, cookie) or how it relates to logoutUser, so the agent learns nothing it couldn't infer from the name alone.

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?

There is no when-to-use guidance, no precondition (e.g. must supply credentials before calling protected endpoints), and no mention of when to prefer logoutUser or getUserByName. Usage is only implied by the tool name.

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