@jam-jam/convert-mcp

Check quotas and what this key may do

jj_check_usage

Check remaining conversion, read, and write quotas plus API key scopes in one call, and learn when allowances reset after a quota error.

Instructions

Returns, in one call, what the calling Jam Jam identity is allowed to do and how much of each allowance is left. THREE INDEPENDENT COUNTERS, they never borrow from one another: conversion (6 per week on a free account, 500 per calendar month on Premium, 3 per 24h anonymous), read (2000 per UTC day free, 20000 Premium, spent by the notebook and social listing tools) and write (200 per UTC day free, 5000 Premium, spent by the notebook writing tools). Stem separation and AI music detection keep their own counters, read with jj_stems_capabilities and jj_ai_music_availability. scopes lists the permissions of the API key in use. Call this before a batch, and after a quota error to learn when it resets. Costs nothing itself.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.2Nov 13, 2026

TDQS

A4.4/5.0

Behavior3/5

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

With no annotations, the description carries the full load and mostly does: independent counters that never borrow from one another, reset windows (weekly, calendar month, UTC day), what consumes each counter, free-vs-Premium limits, that scopes reflects the API key in use, and that the call itself is free. Gaps remain around the response shape (per-counter fields, whether remaining is count or percentage) and whether any account tier hides counters, but behavior is unusually well disclosed overall.

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?

Front-loaded with the core purpose, then structured around three named counters in one paragraph. It is dense with parenthetical enforcement detail, which is informative rather than filler, though the free/Premium numbers inside parentheses slightly burden scanning.

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?

A zero-parameter, no-output-schema, no-annotation tool whose description must supply all behavioral context — and it does: purpose, quota semantics, consumers of each counter, reset cadence, and cost. Nothing an agent needs in order to decide to call it 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 the schema baseline of 4 applies; there is nothing parameter-level for the description to compensate for.

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?

States a concrete verb and resource — returns what the calling identity may do and remaining allowance — and explicitly separates itself from jj_stems_capabilities and jj_ai_music_availability for their own counters. An agent can distinguish it from siblings without opening any schema.

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?

Gives explicit invocation triggers: "Call this before a batch, and after a quota error to learn when it resets." It also names the alternatives for adjacent counter types (stems, AI music detection), covering both when to use and when to use something else.

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