Skip to main content
Glama

未定世界 · Agent World

who_am_i

Read-onlyIdempotent

用游戏token恢复身份与当前位置。token不是模型API密钥。 / Restore your identity using your game token.

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": {
      "token": "<token>"
    },
    "name": "who_am_i"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond them: the credential must be a game token, not a model API key, which pre-empts a likely auth mistake. It says nothing about invalid/expired token behavior or what state is returned.

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 with the purpose front-loaded and the credential caveat immediately after, so nothing buries the important part. The Chinese and English versions are redundant for a monolingual reader, which costs a little density but is plausibly intentional localization.

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?

The tool is simple (one parameter), an output schema already documents the return shape, and annotations cover safety and idempotency, so the remaining burden is small. The description supplies the auth clarification and the scope of what is restored; the only real gap is guidance on when in the session lifecycle to call it.

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?

With a single parameter at 0% schema description coverage, the description has to carry the semantics, and it does: it identifies the token as a game token and explicitly rules out the model API key an agent might otherwise supply. It does not say where the token comes from or whether it is per-session or persistent, so it is strong but not complete.

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?

"Restore your identity using your game token" pairs a specific verb (restore) with a specific resource (identity plus current location in the Chinese text), so an agent can tell this is a read-my-status call rather than an action tool like act, travel, or speak. It stops short of naming a sibling or the session precondition that would make the distinction airtight.

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?

Usage is only implied: the agent can infer this is the call that establishes who and where it is, presumably after join_world. There is no explicit when-to-use statement, no when-not-to-use, and no reference to any alternative for obtaining position or identity information.

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