Skip to main content
Glama
Sign In
jade-mcp

jade-mcp

by choiyounggi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

계정 설정 페이지 열기

jade_onboarding
Idempotent

Open a local browser page to enter or update JADE account credentials and return its URL; use it when your password changes or you switch accounts, keeping passwords out of chat.

Instructions

JADE 계정(회사코드·아이디·비밀번호)을 입력·변경하는 로컬 설정 페이지를 브라우저로 열고 주소를 돌려준다. 계정이 없으면 다른 jade 도구도 이 페이지를 연다. 비밀번호가 바뀌었거나 다른 계정으로 바꿀 때 쓴다. 비밀번호는 절대 대화로 받지 말고 이 페이지에만 입력하게 안내한다. 입력값은 로그인으로 확인한 뒤 Keychain 에 저장된다.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses that a browser is launched, that the return value is a URL, that submitted values are validated by an actual login and then persisted to Keychain, and that said side effect is why readOnlyHint is false. It does not say whether the call blocks/waits for the user to finish or what happens if the page is abandoned.

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?

Four short sentences, front-loaded with what opens and what is returned, then when to use it, then the critical safety rule about passwords. No filler or repetition of the title.

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?

With no output schema, the description correctly states the return value is the page address, and it covers credential storage and a mandatory security protocol. The only gap for a browser-launching, state-changing flow is the lack of any note on blocking behavior or what the agent should do after returning the URL.

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 there is nothing for the description to disambiguate; the baseline of 4 applies. The description is consistent in that it explains inputs are collected in the browser page rather than as tool arguments.

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?

States a specific verb and resource: opens a local settings page in a browser for entering/changing JADE account credentials (company code, ID, password) and returns the address. It also implicitly separates this from the sibling prepare/commit tools by noting they route to this same page when no account exists.

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?

Explicitly says when to use it (password changed, switching accounts) and when it is reached indirectly (no account configured, other jade tools open this page). It lacks an explicit exclusion or a named alternative for cases where an account is already valid, but the trigger conditions are clear.

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