Skip to main content
Glama
rendyuwu

Arknights Intelligence MCP

by rendyuwu

Get item drops

get_item_drops
Read-onlyIdempotent

Compare Arknights item drop rates across stages by server and game ID, with optional efficiency ranking based on sanity cost per item.

Instructions

Compare where one Arknights item drops by region + item game_id, sourced from the Penguin Statistics cache. It lists the item's drop across every stage that yields it. Each stage carries its sanity cost, quantity, times, and drop_rate. The times is the sample run count. The drop_rate is the expected number of items per run (quantity divided by times), not a probability. The penguin provenance (snapshot, fetched/expires time, and import time) shared by every stage is hoisted to a single drop_provenance block. A stage repeats a provenance field only when it differs. A stage carries expired:true only when past its cache expiry. Set include_efficiency to add deterministic farming observations, ranked ascending by sanity spent per item. With that flag the ranked observation is the single per-stage list, each row folding the stage facts and its sanity-per-item, so the stages are never listed twice. Without the flag the raw stages list is returned and paged on its own. That ranking is an ordering and evidence, never a best-farm or mandatory verdict. Stage availability, first-clear bonuses, and byproducts/synthesis are not modeled. A stage drop past its expiry is still returned, flagged data_stale. It is downgraded in the ranking, not dropped. A re-sync of the penguin source refreshes the cache. An item's comparison never mixes en/cn stages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverYes
game_idYes
stages_pageNo
efficiency_pageNo
include_efficiencyNo
Behavior5/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds extensive behavioral context: cache source, drop_rate meaning, provenance handling, stale data behavior, and ranking limitations. 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 lengthy but every sentence adds value. It is well-structured, front-loaded with the purpose, and logically organized. Minor redundancy could be trimmed, but overall efficient.

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 the complexity (5 parameters, no output schema), the description comprehensively explains output fields, provenance, paging, ranking behavior, and data staleness. It addresses edge cases and limitations, making the tool's behavior fully predictable.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It explains include_efficiency and pagination behavior in detail, but does not explicitly describe each parameter (e.g., server, game_id, page parameters). The description adds significant value but lacks full parameter mapping.

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 where an Arknights item drops by region and item game_id. It uses specific verbs ('compare', 'lists') and distinguishes from sibling tools (e.g., get_stage_drops for stage-specific drops).

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?

The description implies when to use the tool (comparing drops across regions) and explicitly mentions limitations (stage availability, first-clear bonuses, byproducts not modeled). It does not directly contrast with siblings but provides sufficient context for appropriate usage.

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