Skip to main content
Glama
Sign In
gma3-mcp

gma3-mcp

by nf-s
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Search the fixture-type library

gma3_patch_library

Searches grandMA3, grandMA2, user, and WorldServer fixture libraries by manufacturer, model, or file name so you can find compatible fixture files before importing or patching.

Instructions

Read-only. Searches the fixture types the console can import: its grandMA3 library (a few fixtures plus scenery), its grandMA2 library (about 11 500 fixtures, the main one), the user library and WorldServer downloads (.xml and .gdtf). Every word of query must occur in the manufacturer, model or file name (case-insensitive), e.g. "chauvet festoon" or "mega hex". Each entry has the source, the file name to pass to gma3_patch_import, manufacturer and model, the mode names when the file is readable (grandMA3 and user .xml; grandMA2 .pxml files are encrypted, so their modes are known only after the import: gma3_patch_types then lists them), verified (false for user-library .xml and WorldServer files, whose import is not verified on the console yet; user-library .gdtf is verified) and inShow: show types already matching it by manufacturer and name (importing again would add a duplicate). Scenery (set@ files) is left out unless include_sets. Paginated (limit default 50, max 500; nextOffset is where the next page starts). compact: true lists file names only, per library, with inShow and notVerified (also per library) for the files that have them (default limit 500): use it for a broad query (a manufacturer) and ask for the full entries of the files you need. Every page is cut to about 40000 characters so it fits the client; the result says truncated when it was. gma3_patch_library_add puts a .gdtf or .xml file into the user library. Needs bridge 0.26.0.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum entries (default 50, or 500 with compact; max 500).
queryNoWords to match, e.g. "oppsk wall washer". Omit to list everything.
offsetNoEntries to skip (default 0).
compactNoFile names only, grouped by library, plus inShow and notVerified (per library) where they apply (default false).
sourcesNoLibraries to search (default all).
include_setsNoInclude scenery (set@ files: trusses, buildings, markers).

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?

With no annotations, the description carries the whole burden and delivers: read-only declared up front, pagination defaults, a ~40,000-character page cap reported via truncated, the verified flag's meaning per source, and the encrypted .pxml caveat. This is unusually complete behavioral disclosure.

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

Conciseness3/5

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

Front-loads 'Read-only.' correctly, but the rest is a dense run-on paragraph mixing return fields, pagination, encryption caveats and sibling guidance. Informative yet hard to scan; a few sentences are doing too much work.

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 six-parameter, no-output-schema search tool, the description documents every returned field (source, file name, manufacturer, model, modes, verified, inShow, nextOffset, truncated) and the compact-mode shape. Nothing needed to call or interpret it 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 coverage is 100%, so most parameter meaning is already structured, but the description adds real semantics: query is AND-of-words across manufacturer/model/file name, case-insensitive; compact changes the default limit to 500; include_sets admits only set@ scenery. It goes beyond the schema's examples without contradicting it.

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 (searches fixture types the console can import) and enumerates the four libraries covered. It is clearly distinguishable from sibling gma3_patch_types, which is explicitly relegated to listing modes after import.

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 real routing guidance: use compact:true for a broad query such as a manufacturer, then fetch full entries for the files needed, and it warns that importing an inShow type would duplicate. It doesn't say when to prefer this over gma3_patch_types for simple lookups, but the import-oriented framing makes the context clear.

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