Skip to main content
Glama

query_object

Query any grandMA2 object type by specifying object type and ID. Use list mode to view objects or annotation mode to read user-added text notes.

Instructions

generic query for any grandMA2 object type.

use this for object types without a dedicated tool (e.g. executors, sequences, effects).
for groups, cues, and presets, prefer the specific tools.

Args:
    object_type: MA2 object type (e.g. "executor", "sequence", "effect", "macro")
    object_id: object ID to query (optional)
    mode: "list" to list objects, "annotation" to read user-added text annotation (default: "list").
          note: "annotation" mode reads user-added descriptive text, NOT object properties.

Returns:
    str: raw console response

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_typeYes
object_idNo
modeNolist

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Describes behavior: querying object type with optional ID, list/annotation modes. Clarifies 'annotation' mode reads user-added text, not properties. No annotations provided, so description carries full burden and does so well.

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

Conciseness4/5

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

Well-structured with clear sections but could be slightly more concise. Front-loaded with purpose, followed by guidelines and parameter details.

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 output schema exists, description provides comprehensive coverage: purpose, usage, parameters, return type. Complete for a generic query tool.

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?

With 0% schema coverage, description explains all three parameters: object_type with examples, object_id as optional, and mode with default and note. Adds meaning beyond schema.

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 it's a generic query tool for any grandMA2 object type, distinguishes from dedicated tools, and lists example object types.

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?

Explicitly says when to use this tool (object types without dedicated tool) and when to prefer specific tools (groups, cues, presets). Also explains mode usage.

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