d1jiema-mcp

Open D1Jiema local setup

d1jiema_setup_local

Launch a one-shot localhost form to enter and save your D1Jiema API token; the form closes after saving.

Instructions

Launch a one-shot localhost form for entering the D1Jiema API token. The form closes after saving.

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

Input Schema

Name	Required	Description	Default
`open_browser`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 7, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations only declare the safety profile (write, non-open-world, non-destructive). The description adds real behavioral context beyond that: this is an interactive localhost form, it is one-shot, and it self-closes after saving. It still doesn't say what happens to the captured token or whether any prior config is affected.

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?

Two short sentences, action front-loaded, and the lifecycle detail ('closes after saving') is placed where it matters. No filler.

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?

An output schema exists, so return values need no explanation, and the description covers what the tool does and its interactive lifecycle. It is nearly complete; only the undocumented open_browser flag and sibling-selection guidance are missing.

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 0% for the single open_browser parameter, and the description never mentions it or its default. Because coverage is low, the description was expected to compensate and does not, so it falls below the 3+ baseline.

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 ('Launch') and resource ('one-shot localhost form for entering the D1Jiema API token'), so the agent knows this bootstraps credential entry rather than an API call. It doesn't explicitly contrast itself with siblings like d1jiema_login or d1jiema_settings_update, which is the only thing keeping it from a 5.

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

Usage Guidelines3/5

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

The word 'one-shot' implies first-time/initial setup, which is usable context, but there is no explicit when-to-use-vs-alternative guidance (e.g., versus d1jiema_login or d1jiema_settings_update). Usage must be inferred from the phrase rather than stated.

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

Deploy Server