Skip to main content
Glama
Sign In
voicesmith

voicesmith

by fergo5002
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Verify Audio

verify_audio

Check an audio file for voicesmith watermark and AI-disclosure tags to confirm provenance and disclosure compliance.

Instructions

Check a file for voicesmith's watermark and AI-disclosure tags.

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": "verify_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 disclosure burden, and it says nothing about read-only behavior, permissions, failure modes when no watermark is found, or supported formats. Only the implicit 'check' verb hints at a non-mutating operation, which is a weak substitute for an explicit statement.

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 tightly worded sentence with the object front-loaded and zero filler. It is efficient, though the brevity contributes to the gaps noted in other dimensions.

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?

The output schema covers return values, so the description needn't explain results. However, with no annotations and no schema documentation, the description should clarify what 'watermark' and 'AI-disclosure tags' mean and any input constraints; that is missing.

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?

Single 'path' parameter at 0% schema description coverage; the phrase 'a file' implies the parameter is a file path, which is minimal but useful compensation. Little else is added about acceptable path forms or restrictions.

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?

Specific verb ('Check') applied to a concrete resource (a file) with two named targets: voicesmith's watermark and AI-disclosure tags. None of the siblings (list_voices, speak, doctor, etc.) perform verification, so it is clearly distinguishable, though 'Check' is slightly weaker than 'verify' would be.

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 guidance on when to use this versus alternatives, no prerequisites, and no statement about which files are valid inputs (must they be voicesmith-generated?). The agent must infer all usage context.

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