Skip to main content
Glama
Sign In
Galgame MCP

Galgame MCP

by YeXuanHs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

audio_probe

Determine native audio encoding and extract container metadata to enable correct decoding for game localization workflows.

Instructions

Detect native audio format and decode container hint.

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": {
      "path": "<path>"
    },
    "name": "audio_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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 the full burden of behavioral disclosure. It does not state whether the tool is read-only, what it returns (e.g., JSON structure), or what 'decode container hint' means. This is a significant gap for a probe tool.

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 a single, front-loaded sentence with no filler. Every word contributes to the purpose statement, making it highly concise and structurally sound.

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

Completeness2/5

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

Given the simple interface (1 parameter, no output schema, no annotations), the description is too sparse. It omits return values, what a 'container hint' is, and any error or edge-case behavior. This leaves the agent with insufficient context to confidently invoke the tool and interpret results.

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

Parameters2/5

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

The schema lists only a 'path' string parameter with no description, and schema coverage is 0%. The description does not explain the path parameter or its expected format beyond implying a file path. This adds minimal value over the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action: 'Detect native audio format and decode container hint.' The verb 'detect' plus 'native audio format' gives clear purpose, and it distinguishes from siblings like audio_decode and audio_list_formats. However, 'decode container hint' is ambiguous, preventing a perfect score.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs alternatives. It does not mention audio_decode, audio_list_formats, or any prerequisites. The usage is only implied by the name and description (e.g., probe an audio file before decoding), but no when-to-use or when-not-to-use is stated.

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