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

掌锤公开查询 MCP

by Vper496
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_report

Read-onlyIdempotent

Retrieve a published Warhammer 40K report with paginated unit statistics and optional faction, release, or detachment filters for read-only analysis.

Instructions

读取报告及细分统计首页；单位每页20行，按返回的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_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idYes
faction_idNo
release_idNo
units_pageNo
detachment_idNo
dataset_revisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / units_page
      Added value: +{
+  "default": 1,
+  "maximum": 10000,
+  "minimum": 1,
+  "title": "Units Page",
+  "type": "integer"
+}
  2. First observedv0.1.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds real behavioral detail beyond them: 20 unit rows per page, continuation via the returned next_page, and a filter-scope caveat. It does not say what the breakdown section contains or whether other sections paginate.

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 compact sentence cluster with semicolons, front-loading the read action before pagination and filter caveats. Dense and largely waste-free, though the pagination clause is slightly cryptic about which section's next_page is meant.

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

Completeness3/5

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

No output schema, so the description correctly covers the next_page return contract and paging limit, and the annotations handle the safety profile. Still incomplete for a 6-parameter tool: a third of the inputs have no stated meaning anywhere.

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 6 parameters, so the description carries the full burden. It only illuminates two of them — units_page (20 rows per page, follow next_page) and detachment_id (do not apply to unit rows) — leaving report_id, faction_id, release_id and dataset_revision unexplained.

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?

States a specific verb+resource: reads a report plus its breakdown-statistics first page. It is distinguishable from list_reports (list) and get_roster (roster) by the 'report + sub-statistics' framing, though it never names a sibling to contrast with.

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 only implied — you call it when you have a report_id and need its detail. The one explicit guideline is a negative one: the detachment filter must not be applied to unit rows. No guidance on when to prefer list_reports or get_matchups instead.

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