Skip to main content
Glama
rendyuwu

Arknights Intelligence MCP

by rendyuwu

Get operator

get_operator
Read-onlyIdempotent

Retrieve an Arknights operator's key facts including summary, phases, skills, talents, modules, and image references by specifying server and game ID.

Instructions

Fetch one Arknights operator's facts by region + game_id. The default response is compact identity + a summary (rarity, profession, subclass, position, tags, and how many phases/skills/talents/modules exist) + provenance; set include_phases / include_skills / include_talents / include_modules to add each (bounded) heavy section. When the image-reference source is enabled, an additional image_refs list of derived portrait/avatar/skin art URLs is included. Each ref carries a variant label naming the art: e0 (base elite-0), e2 (elite-2), base (avatar), or skin. en/cn are never mixed. Skill, talent, and module effects include the in-game effect description template (when present in the source) alongside raw blackboard key-value data; read the template to interpret the values, and do not infer mechanics from a key name alone. A skill's template is emitted once as the skill's description when it is the same at every level; it appears on a level only when the wording differs between levels. For a module's trait_changes and talent_changes: repeated identical entries for one change are collapsed into a single row. A bundle that is the same at every level is listed once on the module (as trait_changes or talent_changes) and omitted from each level. A talent change tagged applies_to "token" affects the operator's summon or token rather than the operator. To compare one operator's modules across their upgrade levels side by side, or for evidence-backed module observations, use compare_operator_modules instead. A glossary of common blackboard keys is provided in this server's instructions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverYes
game_idYes
include_phasesNo
include_skillsNo
include_modulesNo
include_summaryNo
include_talentsNo
include_provenanceNo
Behavior5/5

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

The description discloses many behavioral traits beyond the annotations (readOnlyHint, idempotentHint): default response structure, when image_refs appear, language mixing rules, skill/talent/module effect handling, template emission conventions, and module change collapsing. No contradictions with annotations.

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 description is long but well-structured and front-loaded with the core purpose. Every sentence adds value, though a slight tightening could improve conciseness. It remains highly informative without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters, no output schema, and the complexity of the data, the description covers default behavior, optional sections, image refs, language handling, effect template details, module collapsing, token talent, and sibling tool alternative. It is complete for correct invocation and interpretation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining the purpose and effect of each include parameter (phases, skills, talents, modules, summary, provenance) and the image_refs condition. It clarifies the meaning of server and game_id as region+game_id.

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 starts with a clear verb+resource: 'Fetch one Arknights operator's facts by region + game_id.' It explicitly states the tool's function and distinguishes it from siblings like search_entities (search) and compare_operator_modules (comparison).

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool and when to use alternatives: 'To compare one operator's modules across their upgrade levels side by side, or for evidence-backed module observations, use compare_operator_modules instead.' It also explains which optional parameters to include for specific data sections.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rendyuwu/arknights-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server