Skip to main content
Glama

dungchua_get_tone_guide

Read-onlyIdempotent

Retrieve acoustic pitch contour, phonation cue, and minimal-pair drill specifications for any of the 6 Northern Vietnamese tones (ngang, huyen, sac, hoi, nga, nang).

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": {
      "tone": "<tone>"
    },
    "name": "dungchua_get_tone_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneYesTarget Northern Vietnamese tone key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is fully covered. The description contributes real but limited context by naming the three content classes returned (acoustic pitch contour, phonation cue, drill specifications), which tells the agent what the guide contains. It does not describe depth, format, or how the drill specs relate to the sibling evaluation tool.

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?

One front-loaded sentence with no filler, and the verb and resource lead. It is dense with domain jargon ('phonation cue', 'minimal-pair drill specifications') but each term carries content rather than padding.

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?

For a one-parameter, read-only lookup with no output schema, the description is nearly sufficient: it names the returned content categories so the agent knows what to expect. What is missing is any sense of the response shape or depth (e.g. whether the contour is a numeric array or prose), which matters more because no output schema exists.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter is a fully enumerated tone key with its own description, so the schema already does the work. The description restates the same six tone keys without adding format, casing, or fallback guidance; baseline 3 is appropriate.

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?

A specific verb ('Retrieve') plus a well-defined resource, and it enumerates exactly what the resource contains (pitch contour, phonation cue, minimal-pair drill specs) and its domain (6 Northern Vietnamese tones, all named). This is clearly distinguishable from the sibling evaluate_recording_gates, which evaluates rather than retrieves reference material.

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?

There is no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no alternatives named. The phrase 'for any of the 6 tones' weakly implies a per-tone lookup, but an agent gets no instruction about sequencing or when this should be called instead of another tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.