@jam-jam/convert-mcp

Find my current AI music analysis

jj_ai_music_current

Retrieve your current or most recent AI music analysis, or null if none exists. Use it to find the ID of a running analysis, since only one unfinished analysis per account can exist.

Instructions

Returns the caller's current or most recent AI music analysis, or null when there is none (GET /ai-music/jobs). Use it to find the id of a running analysis, since only one unfinished analysis per account can exist. Needs the queue:read scope. Costs no quota.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.2Nov 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses the null return case, the account-level invariant that only one unfinished analysis can exist, the required queue:read scope, and that the call costs no quota. It only omits detail on the shape of the returned analysis object.

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?

Three short sentences, front-loaded with the return value and the null case, then usage, then the operational constraints. No sentence is filler; scope, cost, and invariant each add distinct information.

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 parameterless, read-only lookup with no output schema and no annotations, the description covers the essential operational facts an agent needs to call it safely and interpret a null. It could say slightly more about what the returned analysis contains if not finished, but nothing critical 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the implicit 'caller's account' scoping, which it does state. Baseline 4 applies for a parameterless tool.

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 states a specific verb and resource ('Returns the caller's current or most recent AI music analysis') plus the empty case ('or null when there is none') and the underlying endpoint. It does not explicitly name a sibling such as jj_ai_music_get_job or jj_ai_music_history to contrast with, so differentiation is implied rather than stated.

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?

'Use it to find the id of a running analysis' gives a concrete job-to-be-done and implicitly routes the agent away from per-job lookups that require an id it does not yet have. It stops short of an explicit when-not statement or a named alternative.

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