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

@jam-jam/convert-mcp

by titouannwtt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

AI music detection: availability, limits and quota

jj_ai_music_availability

Check whether AI music detection is available, including upload limits, accepted links, and remaining daily and monthly quota with exact reset times before analyzing audio or after a 429.

Instructions

Reports whether the AI music detection is available (GET /ai-music/availability): upload size and duration limits, whether links are accepted, and the remaining daily and monthly quota with exact reset times (quota.daily.resetsAt, quota.monthly.resetsAt, epoch milliseconds, UTC). Quotas: visitor 2/day and 5/month, free account 5/day and 50/month, Premium 30/day and 300/month, shared between website, app and API keys; failures and cancellations are refunded. Call it before jj_ai_music_analyze and after a 429. Costs nothing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.9/5.0
Behavior5/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: it discloses that quota is shared across website, app and API keys, that failures and cancellations are refunded, per-tier quota numbers, and that the call is free. It also flags the 429 relationship, which is the key behavioral risk an agent would otherwise hit blind.

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?

One tight paragraph, front-loaded with the core purpose before quotas, refund semantics, and call timing. Every clause carries usable information — the parenthetical path, reset-time format, and tier numbers all affect how an agent interprets the result; nothing is filler.

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?

For a zero-parameter, read-only availability endpoint with no output schema, the description supplies everything needed: what is returned, the exact units and timezone for reset timestamps, the quota table by tier, and refund rules. Nothing an agent needs to interpret the response or decide when to call 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 no parameters and schema coverage is 100%, so the baseline of 4 applies. The description's field-level detail ('quota.daily.resetsAt', epoch milliseconds, UTC) documents the response rather than inputs, which adds value but does not change the parameter picture.

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 specific verb and resource ('Reports whether the AI music detection is available') and enumerates the exact payload contents: upload size and duration limits, link acceptance, and remaining daily/monthly quota with reset times. It also names the underlying endpoint, and explicitly contrasts itself with jj_ai_music_analyze, so an agent can distinguish it from siblings without opening a 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 call conditions: 'Call it before jj_ai_music_analyze and after a 429.' That is both a positive trigger and an error-recovery trigger tied to a named alternative, plus the reassurance that it 'costs nothing' removes any hesitation about calling it preemptively.

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

Deploy Server

Other Tools