Skip to main content
Glama
Sign In
GMA2 MCP

GMA2 MCP

by chienchuanw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

read_cue_info

Retrieve and parse cue information including label, fade time, and CMD field for a specific cue in a sequence using sequence and cue IDs.

Instructions

Read cue information for a specific cue in a sequence.

Retrieves and parses cue data including label, fade time, and CMD field.

Args:
    sequence_id: Sequence ID containing the cue
    cue_id: Cue ID (int or str for decimal cue numbers like "2.5")

Returns:
    dict with parsed cue info and raw response

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sequence_id": "<sequence_id>",
      "cue_id": "<cue_id>"
    },
    "name": "read_cue_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
sequence_idYes
cue_idYes

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 provided; description does not disclose non-obvious behaviors like prerequisites, side effects, or idempotency. It only states it retrieves data, which is implicit from the name.

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?

Concise two short paragraphs with clear Args/Returns section. No redundant or extraneous text.

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?

Covers parameters and basic return concept, but output format is vague ('parsed cue info') and no expected keys are listed. With no output schema, more detail would improve completeness.

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?

Despite 0% schema coverage, description adds meaning: sequence_id is 'Sequence ID containing the cue', cue_id is explained with type guidance and example ('int or str for decimal cue numbers like "2.5"'). This compensates well.

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?

Description clearly states 'Read cue information for a specific cue in a sequence' with specific verb and resource. It distinguishes from siblings like get_cue_annotation or list_cues by specifying details like label, fade time, and CMD field.

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?

No explicit guidance on when to use vs alternatives. While the verb 'read' implies a safe query, no conditions or exclusions are mentioned.

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