Jiji MCP

jiji_connection_status

Read-onlyIdempotent

Check whether the extension-free companion is available and Jiji sign-in is visibly active before using marketplace tools, without reading cookies or passwords.

Instructions

Check the extension-free companion and visible Jiji sign-in status. Does not read cookies or passwords.

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

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

B3.3/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context — it does not read cookies or passwords, and it depends on a companion process being present — but it says nothing about what happens when the companion is absent or what failure looks like.

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?

Two short sentences, front-loaded with the core action, and the privacy caveat follows efficiently. Minor jargon ('extension-free companion') costs a little clarity per word spent.

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?

An output schema exists, so return values need not be explained. However, for a zero-parameter status tool the description never defines what 'companion' means or what the agent should do with a negative status, leaving a gap in a tool whose whole job is reporting state.

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 no parameters, so the baseline is 4; there is nothing for the description to document and no missing parameter semantics.

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?

States a specific verb and resource: check the status of the companion process and of the visible Jiji sign-in. This is clearly distinct from siblings such as jiji_open_sign_in (which performs sign-in) and jiji_capabilities, though it never names those alternatives. The slightly cryptic phrase 'extension-free companion' keeps it from a full 5.

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?

There is no explicit when-to-use or when-not guidance and no sibling is named, even though jiji_open_sign_in and jiji_action_status are obvious near-neighbors. An agent must infer that this is the pre-flight check before sign-in or before other calls.

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