Skip to main content
Glama
Sign In
掌锤公开查询 MCP

掌锤公开查询 MCP

by Vper496
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_matchups

Read-onlyIdempotent

Query faction and detachment matchup matrices from published Warhammer 40K reports, with filtering and pagination for browsing results 20 rows at a time.

Instructions

查询阵营或分遣队矩阵，每页20行且先筛后分页；分遣队用next_page继续，阵营按has_next递增page并固定版本与修订。

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": {
      "report_id": "<report_id>"
    },
    "name": "get_matchups"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
matrixNofactions
report_idYes
faction_idNo
release_idNo
opponent_idNo
detachment_idNo
dataset_revisionNo
opponent_detachment_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.0
    • addedInput schema / properties / dataset_revision
      Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^[0-9a-f]{64}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Dataset Revision"
+}
    • addedInput schema / properties / detachment_id
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 160,
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Detachment Id"
+}
    • addedInput schema / properties / matrix
      Added value: +{
+  "default": "factions",
+  "enum": [
+    "factions",
+    "detachments"
+  ],
+  "title": "Matrix",
+  "type": "string"
+}
    • addedInput schema / properties / opponent_detachment_id
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 160,
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Opponent Detachment Id"
+}
  2. First observedv0.1.1

TDQS

B3.3/5.0
Behavior4/5

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

Beyond the safety annotations (readOnly/idempotent/openWorld/non-destructive), the description discloses the important filter-then-paginate behavior, the fixed 20-row page size, and the requirement to keep version/revision stable across page requests. These are non-obvious behavioral traits the annotations do not cover.

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?

A single dense sentence that front-loads the resource scope before the pagination mechanics. No filler, though the information density comes at some cost to readability.

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

Completeness2/5

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

For a 9-parameter, 0%-schema-coverage tool with no output schema, the description omits almost all filter-parameter meaning and the mandatory report_id. It covers pagination well but is far from complete enough for an agent to invoke it confidently with the available filters.

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

Parameters2/5

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

Schema description coverage is 0% across 9 parameters, so the description must shoulder the burden. It clarifies the matrix enum and pagination semantics, but leaves report_id, faction_id, opponent_id, detachment_id, and opponent_detachment_id entirely unexplained. It also references next_page/has_next, which are not schema parameters at all.

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 description names a specific verb/resource pair (查询阵营或分遣队矩阵) and distinguishes the two matrix modes. It is clear what the tool does, though it does not contrast itself against the sibling list_* / get_* tools.

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?

It gives concrete operational guidance for continuing pagination (next_page for detachments, incrementing page via has_next for factions), which is genuinely useful. However, it never states when to choose this tool over alternatives or any preconditions for calling it with the many filter IDs.

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