Skip to main content
Glama

new_show_tool

Create a new empty show on a grandMA2 console. Optionally saves the current show to prevent data loss.

Instructions

create a new empty show on the grandMA2 console.

WARNING: this is a DESTRUCTIVE operation. any unsaved changes to the current
show will be lost. set save_first=True to save the current show before creating a new one.

note: per the grandMA2 manual, NewShow requires a show name. omitting the
name may work on some console versions but this behavior is undocumented.
providing a name is recommended.

Args:
    show_name: name for the new show (recommended — required per official manual)
    save_first: if True, saves the current show before creating a new one

Returns:
    str: confirmation message with warning about unsaved changes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
show_nameNo
save_firstNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description fully discloses the destructive operation, the effect on unsaved changes, the recommended parameter behavior, and the return type (confirmation message), ensuring the agent understands the tool's impact.

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 efficiently structured: a clear one-line purpose, followed by a warning, then parameter explanations, and return type. There is no redundant text, and the most critical information is front-loaded.

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?

Given the tool's complexity (destructive, 2 params, output schema), the description fully covers all necessary aspects: purpose, behavior, parameters, and return value. It also addresses an edge case (omitting show_name) and references the manual, making it complete for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description explains both parameters in detail: show_name is recommended per manual, save_first saves before creating. This adds significant meaning beyond the schema's property definitions and defaults.

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 'create a new empty show on the grandMA2 console,' with a specific verb and resource, and distinguishes itself from sibling tools like load_show_tool and save_show_tool. It also provides necessary caveats about the show name.

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?

The description explicitly warns about the destructive nature and advises setting save_first=True to save the current show, giving clear context for when to use the tool. It could also explicitly mention alternatives, but the warning is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chienchuanw/gma2-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server