AniNest

Overview Schema Source Related Servers Discussions Admin

Arena lineup lookup

arena_lookup

Read-only

Look up defense team compositions for a lineup through a local arena service, using names, aliases, or six-digit IDs. Filter by region and refine results with exclusions or replacements.

Instructions

Look up defence teams for a lineup via the local arena browser service.

Args: defense: the lineup by name — "布丁", "克总", "真琴" … (names, aliases or ids). def_ids: the same thing as six-digit ids, if you already have them. region: arena region id, 1 = mainland, 2 = overseas, 0 = no filtering. limit: how many teams to summarise, 1-6 (display cap, not a game rule). exclude: names to drop before searching ("先排除一个再查"). replace: in-place swaps such as ["宫子->真琴"]; positions are preserved.

Input Schema

Name	Required	Description	Default
`limit`	No
`region`	No
`def_ids`	No
`defense`	No
`exclude`	No
`replace`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.4.2Oct 30, 2026

addedInput schema / properties / def_ids / anyOf

Added value: +[
+  {
+    "items": {
+      "type": "integer"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / def_ids / default
```
Added value: +null
```
removedInput schema / properties / def_ids / items
```
Removed value: -{
-  "type": "integer"
-}
```
removedInput schema / properties / def_ids / type
```
Removed value: -"array"
```

addedInput schema / properties / defense

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Defense"
+}

addedInput schema / properties / exclude

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Exclude"
+}

addedInput schema / properties / replace

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Replace"
+}

removedInput schema / required
```
Removed value: -[
-  "def_ids"
-]
```

First observedv0.1.0Oct 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, non-destructive, open-world and non-idempotent, so the safety profile is covered. The description adds useful context ('display cap, not a game rule', 'positions are preserved' for replace), but says nothing about service availability, failure modes, or result ordering for a tool that depends on a local browser service.

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 purpose sentence is front-loaded and the Args block is compact, with each line contributing parameter meaning rather than restating the name. Sphinx-style formatting is slightly verbose but not wasteful.

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?

With an output schema present and annotations covering safety, the description need only explain intent and inputs, which it does for a tool with no required parameters. The remaining omission is how the team summaries are scoped or ranked, which matters for interpreting results.

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 description coverage is 0%, so the description must carry the burden, and it does: all six parameters get meaning, including the defense/def_ids duality, region coding (1/2/0), the 1-6 limit as a display cap, and a concrete replace syntax example with position semantics. Only minor gaps remain, such as array-length rules or what 'six-digit ids' means numerically.

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?

The first sentence gives a specific verb and resource ('Look up defence teams for a lineup') and names the backing service ('local arena browser service'). It is clearly distinct from the character/portrait/memory siblings, though it does not explicitly say so.

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 implied rather than stated: the agent learns that def_ids is an alternative to defense 'if you already have them' and that region=0 disables filtering, but there is no explicit when-to-use/when-not guidance and no mention of the sibling tools as alternatives.

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

Deploy Server