Skip to main content
Glama

TemPolor MCP Server by useapi.net (third-party)

List artist voices

tempolor_list_artist_voices
Read-onlyIdempotent

List TemPolor's predefined artist voices, ready to sing a song without a sample of your own: itemId (pass it as artistVoiceItemId to tempolor_create_song), name, labels, a sample in vocalUrl and coverUrl. Pages: pass the cursor of the answer while hasNext is true. Your own cloned voices are in tempolor_list_cloned_voices. GET /music/artist-voices.

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

Input Schema

NameRequiredDescriptionDefault
cursorNoThe cursor of the previous page, to read the next one. Omit for the first page.
user_idNoThe TemPolor account (user_id from tempolor_list_accounts) to read with. Required when you have several TemPolor accounts; with one it may be left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavior: the returned fields (itemId, name, labels, vocalUrl, coverUrl) and the pagination loop keyed on a hasNext flag that appears nowhere in the schema. It omits error/empty-result behavior and any rate or permission notes, which keeps it just short of a 5.

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?

A single dense paragraph with the purpose and the sibling distinction front-loaded, then the output fields, then paging, then the endpoint. It is efficient, though the field-list phrasing reads telegraphically and requires a second pass.

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?

For a two-optional-parameter read-only list tool with no output schema, the description supplies the return shape, pagination mechanics, the cross-tool handoff, and the sibling alternative. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so the baseline is 3, but the prose adds meaning the schema lacks: cursor is tied to the response's hasNext flag rather than just "the previous page." user_id is left to the schema, which explains it adequately.

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?

Opens with a specific verb and resource ("List TemPolor's predefined artist voices") and immediately scopes it with "ready to sing a song without a sample of your own." It explicitly separates this from tempolor_list_cloned_voices, so an agent can pick the right list tool without opening either schema.

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

Usage Guidelines5/5

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

Names both the condition (no sample of your own) and the alternative ("Your own cloned voices are in tempolor_list_cloned_voices"), plus the downstream step of passing itemId as artistVoiceItemId to tempolor_create_song. Pagination instructions (cursor while hasNext is true) cover the only other usage decision.

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.

Resources