Skip to main content
Glama
Sign In
vocametrix

vocametrix

by Vocametrix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vocametrix_calculate_cpp

Calculates Cepstral Peak Prominence (CPP) from a sustained vowel to assess voice quality. Higher CPP indicates less breathiness or hoarseness.

Instructions

Calculate Cepstral Peak Prominence (CPP) from a sustained vowel. Higher CPP = better voice quality. Typical normal CPP: 20–28 dB. Clinically sensitive to breathiness and hoarseness.

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": {
      "sustainedVowelPath": "<sustainedVowelPath>"
    },
    "name": "vocametrix_calculate_cpp"
  }
}

Input Schema

NameRequiredDescriptionDefault
sustainedVowelPathYesAbsolute path to a WAV audio file on the local filesystem

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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. It discloses the purpose and typical values but does not mention side effects, permissions, output format, or any behavioral constraints beyond calculation.

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 two concise sentences with no filler. The first sentence front-loads the purpose, and the second provides useful interpretive context.

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?

Given no output schema, the description adequately explains input and interpretive value, but lacks details on output format and behavioral context (e.g., side effects, prerequisites).

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 description adds interpretive value (normal range, clinical sensitivity) but does not add parameter-level details beyond what the schema already provides.

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?

The description clearly states it calculates Cepstral Peak Prominence (CPP) from a sustained vowel. It is distinct from other sibling calculate_* tools by specifying the exact metric and input.

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?

Usage is implied by the metric's name and clinical context (e.g., breathiness, hoarseness), but the description does not explicitly guide when to use this tool versus alternatives like calculate_hnr or calculate_avqi.

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