Skip to main content
Glama

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

List running jobs

tempolor_list_running_jobs
Read-onlyIdempotent

The songs and instrumentals this API is tracking now (job_id, started, elapsed mm:ss, replyUrl, replyRef) and the healthy accounts with a free slot (user_id, maxJobs, executing, available). The first check when a create tool answers 429: each account runs at most its maxJobs jobs at once. Everything on an account, web app included, is in tempolor_list_music. GET /scheduler/available (its executing list is GET /scheduler).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is the capacity model: each account runs at most maxJobs jobs at once, and a saturated account has no free slot. That constraint semantics is genuinely useful beyond the structured fields. It doesn't describe ordering, pagination, or what an empty result means.

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?

Content is front-loaded: the returned field sets come first, then the 429 use case, then the capacity rule. Every sentence carries information. The trailing raw endpoint references (GET /scheduler/available, GET /scheduler) are implementation detail that adds density without much decision value for an agent.

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

Completeness4/5

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

There is no output schema, so the description correctly compensates by listing the returned fields for both result sets. Combined with the capacity/429 semantics, an agent has enough to call it and interpret the result. Minor gaps remain around result ordering and whether both sections are always present.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. The schema is empty and fully consistent with the description.

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 names both resources returned — songs/instrumentals currently tracked, plus accounts with a free slot — and enumerates the fields of each, so the agent knows exactly what comes back. It also distinguishes itself from tempolor_list_music, which covers everything on an account including web app. It stops short of a clean verb-first statement (the title carries 'List'), so a 4 rather than 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 gives a concrete triggering condition: 'The first check when a create tool answers 429', which tells the agent when this tool is the right call. It also implies the alternative for a full inventory by pointing at tempolor_list_music. There is no explicit when-not-to-use or guidance for non-429 scenarios.

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