Skip to main content
Glama

has_tag

Read-onlyIdempotent

Check if an object owns a specific gameplay tag and return a boolean. Verify the tag exists first, then use it for single-tag state checks like stunned or alerted.

Instructions

Does this object own this gameplay tag: the single-tag state check (is it stunned, is it alerted, is it a valid target) as a plain bool. The cheapest of the tag predicates -- has_any_gameplay_tags / has_all_gameplay_tags / has_none_gameplay_tags take a list, get_object_tags returns everything. Verify the tag exists first (find_gameplay_tag): an unregistered string becomes an empty tag and returns false exactly like a genuine miss.

Returns: { object_path: string, tag_name: string, has_tag: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tag_nameYesName of the tag to check for
object_pathYesPath or name of the object to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds a non-obvious failure mode that structured data cannot express: an unregistered tag string degrades to an empty tag and returns false identically to a genuine miss. It also characterizes the call as the cheapest of the tag predicates, which informs call-ordering decisions.

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?

Three sentences, front-loaded with the definition, then the sibling differentiation, then the caveat, then the return shape. Every clause earns its place, including the Returns line that compensates for the missing output schema. No filler or restatement of the title.

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?

For a two-param read predicate with no output schema, the definition covers purpose, alternatives, prerequisite validation, the silent-false-negative edge case, and the return shape. Nothing an agent needs in order to call it correctly or interpret the result is missing.

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 100%, so the two parameters are already self-documented and the baseline is 3. The description adds semantic depth beyond the schema by explaining how tag_name resolves (owning vs. mere existence) and what happens when the tag_name is not registered, which directly affects how the parameter must be supplied.

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?

States a specific verb and resource ('Does this object own this gameplay tag') and immediately frames it as the single-tag state check returning a plain bool. It explicitly distinguishes itself from the batch predicates (has_any/has_all/has_none) and get_object_tags, so the agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

Names the alternatives and the condition that selects them ('the cheapest of the tag predicates', list-taking siblings take a list, get_object_tags returns everything). It also gives a concrete prerequisite workflow ('Verify the tag exists first (find_gameplay_tag)'), which is exactly the when-to-do-what guidance an agent needs.

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