Skip to main content
Glama

Sign in and get an API key

sign_in

An existing catchy-me account: email and password -> an API key for this MCP server (shown once). The web's login limits apply. [REST: POST /api/auth/login]

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

Input Schema

NameRequiredDescriptionDefault
langNoThe account's language: ru, en, es (Spanish), de (German), fr (French), pt (Brazilian Portuguese) or ja (Japanese); the messages, the emails and the texts of its searches. Default en.
emailYes
key_daysNoLifetime of the key in days; null = no limit. Default 365.
key_nameNoName of the API key in Settings (default «MCP agent»).
passwordYes
key_accessNofull

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"The account's language (messages, the texts of its searches). Default en."New value: +"The account's language: ru, en, es (Spanish), de (German), fr (French), pt (Brazilian Portuguese) or ja (Japanese); the messages, the emails and the texts of its searches. Default en."
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "ru",
      -  "en"
      -]New value: +[
      +  "ru",
      +  "en",
      +  "es",
      +  "de",
      +  "fr",
      +  "pt",
      +  "ja"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already disclose non-readOnly, non-destructive, non-idempotent, closed-world behavior. The description adds important context that the key is shown once and that web login limits apply, though it does not explicitly say each call creates a new key or describe failure behavior.

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?

The definition is two compact sentences with the core login-to-key flow front-loaded. The REST endpoint in brackets is useful metadata without disrupting readability.

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 core return value (an API key shown once) is explained despite there being no output schema, and annotations cover safety traits. However, the optional key settings are left entirely to the schema, and key_access remains semantically under-specified for an agent configuring the key.

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?

Schema description coverage is only 50%, and the description mentions only email and password, ignoring lang, key_days, key_name, and key_access. key_access in particular has no schema description, and the description does nothing to clarify whether it controls key scope.

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 states a specific flow: existing catchy-me account credentials produce an API key for this MCP server. The word "existing" distinguishes it from sign_up, and the REST endpoint adds useful specificity.

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

Usage Guidelines4/5

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

It clearly scopes usage to an existing account, implicitly steering new users toward sign_up rather than this tool. It does not explicitly name the alternative or spell out when to re-authenticate instead of managing an existing key.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources