Skip to main content
Glama
Sign In
GMA2 MCP

GMA2 MCP

by chienchuanw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_shows_tool

List available show files on a grandMA2 console with optional filter pattern to narrow results.

Instructions

list available show files on the grandMA2 console.

Args:
    filter: optional filter pattern (e.g. "Mac*" to list shows starting with Mac)

Returns:
    str: raw console response with show file listing

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": "list_shows_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions listing and returns raw response, but does not disclose whether the tool is read-only, destructive, or requires any permissions. Minimal behavioral context.

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?

The description is very concise: two sentences for purpose and one parameter explanation. No fluff, front-loaded with main action. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity (1 param, no required, output schema present), the description is adequate but could be more complete: e.g., mention ordering, behavior on empty result, or error scenarios. It doesn't cover edge cases or full behavior.

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?

The only parameter 'filter' has 0% schema description coverage. The description adds meaning by explaining it as an optional filter pattern with an example ('Mac*'). This adds value beyond the schema, though syntax details are minimal.

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?

The description clearly states the verb 'list', the resource 'available show files', and the context 'grandMA2 console'. It distinguishes from sibling tools like 'load_show_tool' and 'new_show_tool' that operate on shows but do different actions.

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

Usage Guidelines3/5

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

The description implies usage (when you want to see available shows) but does not explicitly state when to use this tool vs. alternatives or when not to use it. No mention of exclusion criteria or alternative tools for listing other resources.

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