Skip to main content
Glama

login

Re-authenticate with crack.wrtn.ai by completing the displayed sign-in window, then close it to restore access when prompted.

Instructions

크랙 로그인을 다시 한다. 로그인 창이 뜨면 로그인하고 창을 닫아 주세요. 보통은 필요할 때 자동으로 안내되니 직접 부를 일은 거의 없음.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it discloses the key operational behavior: a login window appears, the user must log in and close it, and it's usually auto-triggered. This human-in-the-loop interaction is important context that the schema doesn't provide. It doesn't cover failure/success behavior or auth-state changes, but it covers the critical interaction.

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

Conciseness4/5

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

Three short sentences with zero waste, and the core action is stated first. The informal tone is a minor readability ding, but every sentence adds useful information (what it does, the interaction, when to skip it).

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

Completeness4/5

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

For a zero-param, no-output-schema, no-annotation tool, the description covers purpose, the interaction flow, and when not to call it. It's nearly complete; only failure behavior and session-state effects are missing, which are relatively minor for a login utility.

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

Parameters4/5

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

The tool has zero parameters, so there's nothing to document in the description. The schema coverage is 100% and there are no params, which is the baseline 4 case.

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?

Names a specific verb and resource: re-login to the Crack service. This is clearly distinct from the story-related siblings. It's slightly less crisp because it says it 'does a login again' rather than describing the action plainly, but the purpose is unambiguous.

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?

Provides explicit when-not-to-use guidance: 'usually you'll be guided automatically when needed, so you rarely need to call it directly.' This tells the agent it should almost never invoke it proactively. The description doesn't name an alternative, but the negative guidance is quite actionable.

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