Skip to main content
Glama

dungchua_evaluate_recording_gates

Read-onlyIdempotent

Evaluate whether a learner audio frame summary passes Đúng Chưa's acoustic DSP admission gates (SNR >= 10 dB, voiced frames >= 25, voiced ratio >= 0.45) or must ABSTAIN.

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": {
      "snr_db": "<snr_db>",
      "clean_voiced_frames": "<clean_voiced_frames>",
      "clean_voiced_ratio": "<clean_voiced_ratio>"
    },
    "name": "dungchua_evaluate_recording_gates"
  }
}

Input Schema

NameRequiredDescriptionDefault
snr_dbYesMeasured signal-to-noise ratio in dB.
clean_voiced_ratioYesRatio of voiced frames (0.0 to 1.0).
clean_voiced_framesYesCount of clean voiced F0 frames.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is lighter. It adds real signal by disclosing the concrete gate thresholds and that the outcome may be ABSTAIN, which is behavior the annotations cannot convey. It stops short of saying what the response looks like when a specific gate fails.

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?

A single front-loaded sentence with the thresholds grouped parenthetically and the ABSTAIN outcome at the end. No filler or restated name.

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 simple, closed-world, read-only three-parameter gate check with full schema coverage and annotations, the definition is nearly sufficient. The one remaining gap is the return shape (pass/fail plus which gate failed), which no output schema exists to cover.

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?

Schema coverage is 100%, so the names and per-parameter descriptions are already documented and a 3 would be the baseline. The description goes further by attaching each parameter to its pass threshold (SNR >= 10 dB, voiced frames >= 25, voiced ratio >= 0.45), which the schema itself does not state.

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?

States a specific verb (evaluate) and a precise resource: whether a learner audio frame summary passes the acoustic DSP admission gates. The exact gate thresholds and the ABSTAIN outcome make the tool's scope unambiguous and clearly distinct from a tone-guide lookup sibling.

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?

Implies the usage context well — feed in frame-summary metrics and learn whether they clear the gates or must abstain — but it never states prerequisites, when not to call it, or what alternative to use if the frame summary is unavailable. Guidance is inferable rather than explicit.

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.