Skip to main content
Glama
Sign In
GMA2 MCP

GMA2 MCP

by chienchuanw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

query_timecode

Retrieve timecode pool status or configuration. Optionally specify a timecode ID to get details for a specific timecode, or omit to list the entire pool.

Instructions

Read timecode pool status / configuration.

Args:
    tc_id: Specific timecode ID (optional; lists the whole pool if omitted)

Returns:
    str: raw console response with timecode 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": "query_timecode"
  }
}

Input Schema

NameRequiredDescriptionDefault
tc_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

States it reads and returns raw console response, implying no side effects. However, without annotations, it lacks explicit safety guarantees, error conditions, or permissions needed.

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?

Two concise sentences with argument documentation. Front-loaded purpose, no wasted words, includes return type.

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

Completeness4/5

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

Covers purpose, param behavior, return type. Low complexity (1 optional param, no nested objects), and output schema exists to describe response structure. Lacks example usage or error handling details.

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?

Adds meaning beyond schema: explains that tc_id is optional and omitting it lists the whole pool. Schema had 0% description coverage, so this value is significant, though format of ID is not detailed.

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?

Clear verb+resource: 'Read timecode pool status / configuration'. Distinct from sibling tools like control_timecode, assign_timecode_slot, and create_timecode_pool, which involve modification or creation.

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?

Implicitly indicates read-only usage, but no explicit guidance on when to use vs alternatives (e.g., before modifying with control_timecode) or when not to use.

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