Skip to main content
Glama
@jam-jam/convert-mcp

@jam-jam/convert-mcp

by titouannwtt

List recent stem separations

jj_stems_list_jobs

List recent stem separation jobs, newest first, to recover a job ID or check whether a separation is still running before starting another. Use the returned cursor to page through results.

Instructions

Lists your recent separations, newest first, 30 per page (GET /stem-tool/jobs). Use it to find a job id again, or to see whether one is still running before starting another (only one can run at a time). Pass the returned "next" as "before" for the next page. Costs no quota (read rate limit).

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

Input Schema

NameRequiredDescriptionDefault
beforeNoCursor: the "next" value of the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses ordering, page size, pagination mechanics, quota cost (none, subject to the read rate limit), and the single-job concurrency rule. It does not say which job states or fields appear in the results, or whether older jobs age out, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact paragraph that front-loads the resource and ordering before moving to usage, pagination, and cost. Every sentence contributes a distinct fact with no filler.

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?

For a one-parameter read tool with no output schema, the description covers purpose, pagination, cost, and concurrency, which is nearly everything needed to call it correctly. The main gap is what a returned job entry looks like, which matters somewhat since no output schema exists.

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%, so the baseline is 3, and the description earns an extra point by explaining how to obtain the cursor: pass the returned "next" value as "before". That operational detail goes beyond the schema's bare "Cursor: the 'next' value of the previous page."

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 gives a specific verb and resource ("Lists your recent separations"), plus ordering (newest first), page size (30 per page), and the underlying endpoint. An agent can distinguish it from jj_stems_get_job, which fetches a single job, 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 Guidelines4/5

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

It names two concrete use cases: recovering a job id and checking whether a job is still running before starting another, and it states the constraint that only one separation runs at a time. It stops short of explicitly naming jj_stems_get_job as the alternative for fetching a single known job, so it is clear context rather than full when/when-not routing.

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