Skip to main content
Glama

lint_scripts

Read-only

Lint Luau scripts with Selene across a place's synced script mirror to catch footguns, unused variables, shadowing, undefined globals, and deprecated APIs; reports findings only and changes nothing.

Instructions

Lint Luau with Selene (the standard Roblox linter) over a place's synced script mirror — catches footguns, unused variables, shadowing, undefined globals, and deprecated APIs (file:line). Read-only: reports findings, changes nothing. Scope with paths or lint the whole mirror. Needs Selene installed (auto-detected or TUFAN_SELENE_PATH) and a selene.toml with std="roblox" in the project (else Roblox globals report as undefined).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lint_scripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsNofiles/dirs relative to the script-mirror root (default: the whole mirror)
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.
timeoutSecondsNomax seconds for the run (default 120, max 600)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing setup dependencies (Selene must be installed, auto-detected or via TUFAN_SELENE_PATH), a configuration prerequisite (selene.toml with std="roblox"), and a concrete failure mode — Roblox globals reporting as undefined without that config. Output shape (file:line findings) is also indicated.

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 dense sentences, front-loaded with the action and tool identity, then behavior, then prerequisites. No filler; every clause (linter name, finding types, read-only, setup requirements) carries decision-relevant information.

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?

With no output schema, the description still conveys the return shape (file:line findings), the read-only semantics, and all environmental prerequisites an agent or caller needs to avoid a spurious failure. Nothing material is missing for a zero-required-parameter lint tool.

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 all three parameters are already documented; the description only reinforces that `paths` scopes the run versus defaulting to the whole mirror. Neither `place` nor `timeoutSeconds` gains meaning beyond the schema, so the baseline 3 applies.

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 — 'Lint Luau with Selene ... over a place's synced script mirror' — and enumerates the classes of problems caught (footguns, unused variables, shadowing, undefined globals, deprecated APIs). This is clearly distinguishable from sibling tools like format_scripts or grep_scripts 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 Guidelines4/5

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

Gives clear operational context: scope with `paths` or lint the whole mirror, and states the read-only reporting behavior, which implicitly separates it from mutation siblings such as format_scripts or find_and_replace_in_scripts. It does not explicitly name an alternative or exclusion, so it falls short of a 5.

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