Skip to main content
Glama

get_tagged

Read-only

List every instance path in a place that carries a given CollectionService tag, optionally filtered by class name. Use it to check what a tag-driven script will act on before changing tags.

Instructions

List the paths of every instance in the place that carries a CollectionService tag. Read-only. Use it to check what a tag-driven script will act on. For one instance's tags use tag with action get.

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": {
      "tag": "<tag>"
    },
    "name": "get_tagged"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYesTag name, exactly as set, e.g. "Collectible".
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.
classNameNoOnly return instances of this class or a subclass, e.g. "BasePart".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / className / description
      Previous value: -"only return instances that IsA this class, e.g. 'BasePart'"New value: +"Only return instances of this class or a subclass, e.g. \"BasePart\"."
    • addedInput schema / properties / tag / description
      Added value: +"Tag name, exactly as set, e.g. \"Collectible\"."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description's "Read-only" largely restates that. What it adds beyond the annotations is the shape of the response — a list of instance paths rather than the instances themselves — which matters because there is no output schema. It does not state ordering, result size, or behavior when the tag matches nothing.

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 short sentences: what it returns, the safety note, the motivating use case, then the alternative. Front-loaded with the resource and scope, and no sentence is padding — the redirect to `tag` prevents a wrong invocation.

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 simple read tool with no output schema, the description covers return content (paths), safety, and the alternative route, so an agent can call it correctly. Minor gaps remain around empty results and whether the place parameter changes traversal scope, but nothing blocking is missing.

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%, with each of the three parameters (tag, place, className) documented including an example value, so the schema carries the parameter burden. The description adds only the generic notion of a tag being required and never mentions the place or className filters. Baseline 3 applies when structured fields already do this work.

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?

"List the paths of every instance in the place that carries a CollectionService tag" gives a specific verb (list), a specific resource (instances with a tag), and the exact scope of what is returned (paths). It is immediately distinguishable from the sibling `tag` tool, which the description explicitly points to for the per-instance case.

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?

Two concrete usage signals are given: the positive case ("check what a tag-driven script will act on") and the alternative for the adjacent need ("For one instance's tags use tag with action get"). The agent knows both when to call this and when to route elsewhere, including the action value on the sibling.

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