Skip to main content
Glama
Sign In
Othos MCP

Othos MCP

Official
by othos-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

othos_auth_login_with_personal_token

Create a cookie session using a personal token for authenticated access to Othos.

Instructions

Create a cookie session using an Othos personal token (PAT).

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

Input Schema

NameRequiredDescriptionDefault
tokenNoPAT. If omitted, uses the configured in-memory token.
tokenPathNoOptional path to load PAT from disk.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.5/5.0
Behavior3/5

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

Basic disclosure that it creates a session; no annotations present. Lacks details on side effects (overwrites existing sessions?), error behavior, or prerequisites. Adequate but not thorough.

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?

Single sentence, no wasted words, front-loaded with action and resource. Efficient and clear.

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 simple auth tool with 2 optional parameters and no output schema, the description covers core purpose but doesn't explain what happens when parameters are omitted or if a session is returned. Adequate but not fully complete.

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 coverage is 100%, so schema already documents parameters. Description adds no extra meaning beyond restating that PAT is used. Baseline 3 is appropriate.

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?

Description states action 'Create a cookie session' using a specific resource 'Othos personal token (PAT)'. Clearly distinguishes from siblings like othos_auth_login (different login method) and othos_auth_set_cookie (different context).

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 guidance on when to use this tool versus alternatives like othos_auth_login or othos_auth_set_cookie. Absence of context for selection.

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