Skip to main content
Glama
rendyuwu

Arknights Intelligence MCP

by rendyuwu

Compare operator modules

compare_operator_modules
Read-onlyIdempotent

Compare an operator's modules side by side across selected levels, with stat bonuses, trait changes, talent changes, and upgrade costs. Optionally get evidence-backed observations.

Instructions

Compare one Arknights operator's modules across the requested module levels (a subset of 1/2/3, default all three) by region + game_id. Each module lists its per-level stat bonuses, trait changes, talent changes, and upgrade cost side by side; a level a module does not define is marked present=false. mode facts_only returns the comparison; with_observations adds deterministic, evidence-backed observations (never a mandatory or best-in-slot verdict). en/cn are never mixed. Each stat/trait/talent change includes 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 module's trait template is emitted once as the module's trait_change_description when it is the same at every level; it appears on a level's trait change 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. For an operator's full kit (identity, phases, skills, talents, and modules), use get_operator with include_modules. This tool instead compares modules level by level, and its with_observations mode adds evidence-backed observations. A glossary of common blackboard keys is provided in this server's instructions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNofacts_only
levelsNo
serverYes
game_idYes
Behavior5/5

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

Annotations already indicate read-only and idempotent. The description adds extensive behavioral details: per-level stat bonuses, trait/talent changes, upgrade costs, present=false for undefined levels, collapsed identical entries, bundle handling, token-applies-to, and template/blackboard data. No contradictions.

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?

Front-loaded with main purpose, then detailed behavioral notes. While lengthy, every sentence provides necessary detail for a complex tool. Could be slightly more compact but well-organized.

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 no output schema, the description thoroughly explains the return structure: per-level side-by-side comparison, present=false, trait/talent formatting, bundle handling, mode output differences, and glossary reference. Complete for informed use.

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?

Schema coverage is 0%; description fully compensates by explaining each parameter's meaning and constraints: mode (facts_only vs with_observations), levels (subset of 1/2/3, default all three), server (en/cn), game_id (string). Adds value beyond schema.

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 clearly states the tool compares one operator's modules across specified levels by region and game_id. It distinguishes from sibling get_operator, which returns the full kit. The verb 'compare' and resource 'operator modules' are specific.

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?

Explicitly says to use get_operator for full kit and this tool for level-by-level comparison. Also notes en/cn never mixed and provides context for mode selection.

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