Skip to main content
Glama
Sign In
prts-mcp

prts-mcp

by 3aKHP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

get_operator_archives

Retrieve the archived profile and lore of any Arknights operator using their Chinese in-game name. Fetches character data from PRTS Wiki.

Instructions

获取指定干员的档案资料（使用游戏内中文名，如"阿米娅"）。

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": {
      "operator_name": "<operator_name>"
    },
    "name": "get_operator_archives"
  }
}

Input Schema

NameRequiredDescriptionDefault
operator_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.14
  2. Removedv0.2.13
  3. 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 provided, so description carries full burden. Adds naming convention hint but lacks disclosure of authentication, rate limits, error handling, or what happens if operator is not found.

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?

Single sentence with no waste. Front-loaded with action and resource. Efficient for a parameter with required name hint.

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?

Output schema exists, so return values need not be explained. Description provides basic context but could elaborate on what 'archive data' entails (e.g., background, skills? ). Adequate but not exhaustive.

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?

Schema has 0% description coverage, so description compensates by instructing to use the in-game Chinese name, adding meaning beyond the generic string type.

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?

Description clearly states the action (获取/obtain) and resource (干员的档案资料/operator archive data). It specifies to use the in-game Chinese name, which adds precision. Distinguishes from siblings like get_operator_basic_info and get_operator_voicelines.

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?

Implies usage for retrieving archive data but no explicit guidance on when to use vs. alternatives. No mention of when not to use or prerequisites.

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