Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

See the project's voices

voices_read
Read-only

The voices the project can speak in: the ones it kept (each with its name, its voiceId and its kind: library, designed or cloned), how many voices of its own (designed or cloned together) its plan allows and how many are made, Marsell's stock voices, and what a voice-over costs a minute. A kept voice is used by picking it by name in Create's voice choice, or by passing its name or voiceId wherever a voice is asked for (ask_marsell, a video's voice). Find more with voice_library_search; clone the owner's own with voice_clone.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "voices_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNoThe project's id or exact name. Optional when the account has one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the shape of each returned voice (name, voiceId, kind), plan quota versus actual usage, stock voices, and cost per minute. It does not discuss pagination or formatting, but for a small project-scoped read that is minor.

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?

The returned contents are front-loaded in the first sentence, followed by usage and alternatives, so the agent gets the essentials immediately. The opening sentence is long and comma-chained, which costs some readability but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by enumerating the returned fields, the quota and cost figures, and even the brand-specific stock voices. Combined with the routing to voice_library_search and voice_clone, an agent has everything needed to call this correctly and use the result.

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 'project' parameter is already documented as id-or-exact-name and optional for single-project accounts. The description only reinforces that the result is scoped to 'the project' without adding format or fallback behavior beyond the schema. Baseline 3 applies when the schema carries the semantics.

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?

The description enumerates exactly what is returned: kept voices with name/voiceId/kind, plan allowance and usage of designed/cloned voices, stock voices, and per-minute voice-over cost. It implicitly reads rather than mutates, and names the sibling tools (voice_library_search, voice_clone) that cover adjacent needs. It lacks a crisp leading verb like 'List'/'Returns', which keeps it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains how the returned voices are consumed downstream — pick by name in Create's voice choice, or pass name/voiceId to ask_marsell or a video's voice — and routes the agent to voice_library_search for more voices and voice_clone for cloning the owner's own. That is clear positive guidance plus alternatives, though it never states an explicit 'do not use this if' exclusion.

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

All Marsell toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources