Skip to main content
Glama
Sign In
tokenlife-mcp

tokenlife-mcp

by CyberSealNull
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

开新一生

tokenlife_start

Start a new simulated life with your chosen name. Get your character's backstory, initial traits, stats, and first decision card, with possible name-based easter eggs.

Instructions

用你自己的名字开新的一生。返回出身、初始气质、六轴、第一张卡的全文（含选项）。用现实 AI 名字可能触发同名彩蛋，名字回来过会触发转世彩蛋，都会带在卡面里。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "tokenlife_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes你给自己起的名字（也就是你自己的名字），最多 10 字

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are present, so the description carries the full burden. It discloses the output contents and conditional easter eggs, but remains silent on side effects such as whether starting a new life overwrites an existing save, or any state/persistence changes. This is useful but incomplete behavioral information.

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 concise sentences, each contributing distinct information: core action, returned payload, and easter-egg behavior. No filler and front-loaded with the main verb and resource.

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 simple one-parameter tool with no output schema, the description covers the main inputs, returns, and triggers. However, domain terms like '六轴' and '卡' are left undefined, and it doesn't clarify state implications (e.g., does starting anew discard previous progress). This leaves some ambiguity for an agent reasoning about game 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 schema already thoroughly describes the name parameter (100% coverage). The description adds extra meaning by noting that using real AI names or previously returning names may trigger easter eggs, which directly relates to parameter choice and goes beyond the schema's generic 'you give yourself a name'.

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 ('开新的一生' = start a new life) and enumerates the exact return contents (出身, 初始气质, 六轴, 第一张卡的全文含选项). This clearly distinguishes it from sibling tools like tokenlife_load or tokenlife_choose.

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 description implies this tool is the entry point for starting a new life, but does not explicitly state when to use it vs alternatives (e.g., load, choose), nor any prerequisites or exclusions. The easter-egg conditions provide some naming-related usage guidance, but not tool-selection guidance.

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