Skip to main content
Glama
Sign In
Othos MCP

Othos MCP

Official
by othos-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

othos_auth_login

Authenticate with Othos by providing email and password to obtain and store an access token cookie for subsequent API calls.

Instructions

Login to Othos with email/password. Stores the returned othos-accessToken cookie in memory.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "<email>",
      "password": "<password>"
    },
    "name": "othos_auth_login"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes
passwordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.8/5.0
Behavior4/5

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

The description discloses that the returned access token is stored as a cookie in memory, which is a key behavioral trait. With no annotations provided, this adds useful context for the agent.

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?

Two sentences directly convey the purpose and side effect. No unnecessary words. Front-loaded efficiently.

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?

The description covers the core behavior but omits what happens on success or failure (e.g., return value or error handling). For a login tool, additional context about the response would be helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not add any additional meaning beyond the schema. With 0% schema description coverage, the description should compensate, but it only mentions email/password generically. No details on format or constraints.

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 clearly states the tool logs in with email/password and stores a cookie. It distinguishes from siblings like othos_auth_login_with_personal_token by specifying the authentication method.

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?

While the description implies use for email/password login, it does not explicitly state when to use this over other auth tools (e.g., personal token login). No exclusions or alternatives are mentioned.

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