Jiji MCP

jiji_open_sign_in

Idempotent

Opens Jiji's standard sign-in page in a companion browser so users can complete login themselves without a browser extension or sharing credentials.

Instructions

Open Jiji’s normal sign-in page in the companion browser, without any browser extension. The user completes login there. Never supply passwords or OTPs to this tool.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Oct 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare openWorldHint, idempotentHint, non-destructive behavior, and readOnlyHint=false. The description adds important behavioral context beyond those annotations: the page opens in the companion browser without an extension, the user completes login externally, and credentials must not be supplied.

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?

Three short sentences, front-loaded with the action and followed by the user-handoff rule and security constraint. Every sentence adds practical guidance without repetition.

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

Completeness5/5

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

For a zero-parameter browser-opening tool with annotations and an output schema, the description covers the key context: what opens, where it opens, who completes login, and what must not be passed to the tool. No critical invocation detail is missing.

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 takes zero parameters, so parameter semantics have limited room for added value. The description correctly avoids introducing nonexistent parameters; baseline for a zero-parameter tool is 4.

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 uses a specific verb-resource pair: opening Jiji's normal sign-in page in the companion browser. The phrase 'without any browser extension' and the sign-in focus distinguish it from workflow/search-oriented siblings without needing to name one.

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 establishes the handoff context: the user completes login on the opened page, and the tool must never receive passwords or OTPs. It does not explicitly compare alternatives such as connection-status or workflow tools, but the expected usage is clear.

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