@jam-jam/convert-mcp

List conversion formats

jj_list_formats

Lists the input and output formats the Jam Jam API currently supports, with size, page and duration limits plus account or Premium requirements, so you can confirm valid conversion targets before converting.

Instructions

Lists the input and output formats actually served by the Jam Jam API right now (GET /formats), with their limits (maxBytes, maxPages, maxDurationS) and whether they require an account or Premium. Call this FIRST, before jj_convert_file or jj_convert_text, to know which output ids are valid for a given input. Pass "input" to get the exact list of possible outputs for that one input format. Needs no API key.

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

Input Schema

Name	Required	Description	Default
`input`	No	Restrict the response to the possible outputs from this input format id (as returned by a previous call without "input"). Adds `possibleOutputs` to the result.
`locale`	No	BCP-47 locale for any localized labels, e.g. "fr".

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.2Nov 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that the data is live ('actually served ... right now'), that results include limits and account/Premium gating, and that no API key is required. It stops short of describing the response envelope shape or any rate limiting, so it is not exhaustive.

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?

Four short sentences ordered by importance: what it returns, when to call it, how to narrow it, and the auth requirement. Every sentence carries distinct, actionable information 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?

There is no output schema, and the description compensates by enumerating the returned attributes (limits, account/Premium flags, output ids). For a two-optional-parameter read-only discovery tool this is nearly sufficient; only the exact response structure is left implicit, which is a minor gap for a list endpoint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented structurally. The description's note about "input" ('get the exact list of possible outputs') largely restates the schema's own 'Adds `possibleOutputs` to the result', and the locale parameter is not mentioned at all beyond the schema, so it adds little beyond baseline.

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?

Names a specific verb and resource ('Lists the input and output formats ... served by the Jam Jam API'), plus the underlying endpoint (GET /formats) and the fields returned (maxBytes, maxPages, maxDurationS). An agent can immediately distinguish this discovery tool from the sibling jj_convert_file / jj_convert_text conversion tools.

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?

Explicitly states 'Call this FIRST, before jj_convert_file or jj_convert_text', naming both alternatives and the ordering constraint that selects this tool. It also scopes a sub-use case ('Pass "input" to get the exact list of possible outputs for that one input format'), leaving nothing to inference.

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