Skip to main content
Glama
Sign In
gregario

Warhammer Oracle

by gregario
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

lookup_unit

Look up a Warhammer 40K unit or Kill Team operative datasheet by name. Returns stats, weapons, abilities, and keywords.

Instructions

Look up a Warhammer 40K unit or Kill Team operative datasheet by name. Returns stats, weapons, abilities, and keywords.

Input Schema

NameRequiredDescriptionDefault
factionNoOptional faction name to narrow results (e.g. 'Chaos Space Marines', 'Astartes')
game_modeNoGame mode/edition: defaults to '40k_11e'. Pass '40k_10e' for 10th Edition units, '40k'/'40k_11e' for 11th Edition (current default), or 'kill_team' for Kill Team operatives.
unit_nameYesName or partial name of the unit to search for
datasheet_idNoOptional exact datasheet ID shown for variants that share a name and faction; pass with faction

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.79
    • addedInput schema / properties / datasheet_id
      Added value: +{
+  "description": "Optional exact datasheet ID shown for variants that share a name and faction; pass with faction",
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.2.41
    • changedInput schema / properties / game_mode / description
      Previous value: -"Game mode: '40k' (default) searches 40K units, 'kill_team' searches Kill Team operatives"New value: +"Game mode/edition: defaults to '40k_11e'. Pass '40k_10e' for 10th Edition units, '40k'/'40k_11e' for 11th Edition (current default), or 'kill_team' for Kill Team operatives."
    • changedInput schema / properties / game_mode / enum
      Previous value: -[
-  "40k",
-  "combat_patrol",
-  "kill_team"
-]New value: +[
+  "40k",
+  "40k_10e",
+  "40k_11e",
+  "combat_patrol",
+  "kill_team"
+]
  3. Addedv0.2.8
  4. Removedv0.2.7
  5. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations present, the description carries the full disclosure burden, and it does add value by enumerating the return contents (stats, weapons, abilities, keywords) in the absence of an output schema. It says nothing about failure behavior, fuzzy/partial name matching, or how the optional faction/datasheet_id disambiguate, so coverage is partial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the verb and resource, then the return payload. Every clause earns its place with no redundancy.

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?

For a read-only lookup tool with no annotations and no output schema, the description compensates adequately by listing the returned fields, and the schema covers all parameters. The missing piece is routing versus the sibling search_units, and no statement about lookup failure or partial-match behavior.

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 100%, so the schema fully documents all four parameters including the game_mode enum and default. The description adds 'by name' but no extra nuance on faction, game_mode, or datasheet_id, so the baseline 3 applies.

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 ('look up a Warhammer 40K unit or Kill Team operative datasheet by name') and even names the return contents, so the agent knows exactly what it retrieves. It does not, however, distinguish itself from the sibling search_units, which is a plausible confusion point.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no mention of the obvious alternative search_units or compare_units. 'By name' implies a targeted lookup, but the agent must infer that this differs from a search tool.

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