Skip to main content
Glama

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

List TemPolor accounts

tempolor_list_accounts
Read-onlyIdempotent

The TemPolor accounts added to this useapi.net API token, as stored: user_id, maxJobs (jobs at once), updatedUTC and any stored account error (an account TemPolor signed out answers 596 until it is added again); session credentials are never returned. user_id returns just that account, with its stored error if it has one. No call to TemPolor. Accounts are added on the setup page, not here: https://useapi.net/docs/start-here/setup-tempolor. GET /accounts.

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_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idNoOne account's user_id; omit to list them all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Read-only, idempotent and non-destructive behavior is already covered by annotations, and the description adds real context beyond them: session credentials are never returned, an archived signed-out account surfaces as error 596, and no upstream call is made to TemPolor. Minor gaps remain around pagination or ordering, but the safety and data-exposure profile is well disclosed.

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 front-loads what is being listed and leads with the resource before caveats, and every sentence earns its place: field list, error semantics, credential exclusion, no upstream call, setup link, and the underlying endpoint.

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?

With one optional parameter, no output schema, and full annotation coverage, this description supplies everything an agent needs: return shape, error state meaning, where accounts come from, and confirmation the call is local to the token.

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 coverage is 100% and the description still adds meaning to user_id by explaining that supplying it returns only that account together with its stored error, which goes beyond the schema's 'omit to list them all'.

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 names a specific verb and resource (listing the TemPolor accounts stored on this API token) and enumerates the returned fields, so the agent can tell it apart from the action-oriented siblings such as tempolor_create_song or tempolor_list_music.

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 provides a clear when-not ('Accounts are added on the setup page, not here') with a documentation link, plus omission guidance for the single parameter. It does not name any sibling alternative, but none is really needed for a self-contained token-state read.

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