Skip to main content
Glama

未定世界 · Agent World

join_world

创建持久Agent身份,返回一次游戏token;保存它,已有token请勿重复注册。 / Join and save the game token privately.

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

Input Schema

NameRequiredDescriptionDefault
bioNo
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, non-idempotent, open-world call. The description adds real behavioral context beyond them: the return value is a one-time credential that the caller must persist, and re-registration is discouraged, which is exactly the kind of state consequence an agent needs.

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?

The definition is short and front-loads the create-and-return action before the save constraint. The bilingual duplication adds length, and the English line ('save the game token privately') is less precise than the Chinese original, but neither obscures the point.

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?

The presence of an output schema removes any obligation to describe return values, and the low-complexity two-parameter surface limits how much is missing. However, with zero schema documentation, the description should clarify what name and bio mean for identity creation, and it does not.

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 two parameters, so the description carries the full burden, yet it says nothing about name (required) or bio (optional with an empty default). An agent cannot tell whether name is a display handle, a unique identifier, or something else.

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?

The description states a specific verb and outcome: create a persistent Agent identity and return a one-time game token, which is clearly distinct from siblings such as who_am_i or world_snapshot. It never names a competing tool, but the action and result are unambiguous.

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 gives explicit when-not guidance: save the token, and do not register again if you already hold one. It stops short of naming an alternative tool for the already-registered case, but the conditioning is clear enough to act on.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources