Skip to main content
Glama
elibarnett

kie-mcp

by elibarnett
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

boost_style

NEW — Convert concise style input (e.g. "Pop, Mysterious") into enhanced style description for music generation.

Instructions

NEW — Convert concise style input (e.g. "Pop, Mysterious") into enhanced style description for music generation.

Input Schema

NameRequiredDescriptionDefault
contentYesConcise style description to enhance
max_creditsNoRefuse to submit if the estimated cost exceeds this many credits (overrides KIE_MAX_CREDITS_PER_CALL). Estimates come from published rates; kie bills the actual amount.
estimate_onlyNoReturn the estimated credit cost WITHOUT submitting anything. Use before expensive runs (video, 4K, 1080p upgrades, layer splits).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.8.0
    • addedInput schema / properties / estimate_only
      Added value: +{
+  "description": "Return the estimated credit cost WITHOUT submitting anything. Use before expensive runs (video, 4K, 1080p upgrades, layer splits).",
+  "type": "boolean"
+}
    • addedInput schema / properties / max_credits
      Added value: +{
+  "description": "Refuse to submit if the estimated cost exceeds this many credits (overrides KIE_MAX_CREDITS_PER_CALL). Estimates come from published rates; kie bills the actual amount.",
+  "type": "number"
+}
  2. First observedv4.7.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It never says whether this submits a billable task, whether it is a pure text transform, or what the returned enhanced description looks like, despite max_credits and estimate_only parameters strongly implying credit-spending behavior that goes unmentioned in the description.

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?

A single front-loaded sentence that covers purpose, input, and output. The 'NEW —' prefix is marketing noise that earns no place, but the rest is tight with zero redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple text-transform tool with no output schema and no annotations, the description covers the core purpose but omits what the enhanced output looks like and whether the call consumes credits, which the credit-related parameters make a relevant open question.

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 the schema already documents content, max_credits, and estimate_only thoroughly (including override precedence and estimate semantics). The description's only added parameter meaning is the input example 'Pop, Mysterious', which lightly clarifies expected content format; baseline 3 applies.

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 names a specific verb (convert) and both the input (concise style text) and output (enhanced style description), with a concrete example. It clearly reads as a style-expansion utility rather than a generation tool, though it doesn't explicitly position itself against generate_music, its most likely companion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The phrase 'for music generation' implies the output feeds a downstream generation call, giving implied usage context. There is no explicit statement of when to reach for boost_style versus just passing a style directly to generate_music, and no alternatives are named.

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