Skip to main content
Glama
Sign In
voicesmith

voicesmith

by fergo5002
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Consent Steps

consent_steps

Guides humans through the consent actions required before a cloned voice can render, covering steps AI agents cannot complete.

Instructions

What the human must do before this voice can render. Agents cannot do these steps.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the returned steps are for human action rather than agent execution, but says nothing about whether the tool is read-only, what permissions are required, or what side effects may occur beyond the output schema.

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?

Two short sentences, front-loaded with the core constraint that this is a human-only prerequisite, with no filler. The extreme brevity is efficient but leaves gaps that a slightly longer definition could address.

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?

An output schema exists, so return-value details need not be explained, and the description conveys the human-only scope. Yet with a required 'name' parameter undocumented and no annotations to cover safety or behavior, the definition is only minimally complete for calling the tool correctly.

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 sole parameter 'name' has 0% schema description coverage, and the description never explains whether it refers to the voice name, a human's name, or a consent identifier. It adds no meaning beyond the schema's bare string type.

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?

States that the tool provides the steps a human must perform before a voice can render, and explicitly says agents cannot perform these steps. It distinguishes the tool from siblings like speak or list_voices by focusing on human prerequisites, though it lacks a direct verb such as 'returns' or 'lists'.

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 usage when a voice requires human consent before rendering and warns that agents cannot execute the steps themselves. However, it gives no explicit when-not cases or alternatives such as doctor, verify_audio, or job_status.

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