mdmagic

estimate_conversion_cost

Read-onlyIdempotent

Estimate credit cost for a conversion BEFORE running it. Returns word count, page calculation (300 words/page), and a credit breakdown by format and template type. Use this when the user asks 'how much will this cost?' or when you suspect a conversion might exceed their balance — convert_document refuses to run if credits are insufficient, so estimating first is friendlier.

Input Schema

TableJSON Schema

Name	Required	Description
`content`	Yes	Markdown content to estimate credit cost for
`pageSize`	No	Page size for the document
`orientation`	No	Page orientation
`outputFormat`	Yes	Output format(s): docx (DOCX only), pdf (DOCX+PDF), html (DOCX+HTML), all/all-formats (DOCX+PDF+HTML)
`templateName`	Yes	Template ID or name (UUID for custom templates, name for system templates)

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already provide readOnlyHint (true) and destructiveHint (false); description adds that it returns word count and credit breakdown, but does not deeply disclose behavior beyond what annotations convey.

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?

Two sentences, front-loaded with purpose and output, followed by usage guidance; every word contributes value.

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?

Though no output schema, the description explains return structure (word count, page calc, credit breakdown) and use case context; could be enhanced with explicit return type format but is sufficient.

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 coverage is 100%, so the description does not add new parameter-level meaning beyond the schema descriptions; baseline 3 is appropriate.

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?

The description clearly states the tool estimates credit cost before conversion, returns word count, page calculation, and credit breakdown, and distinguishes itself from convert_document by noting it runs before conversion.

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 tells when to use: when user asks about cost or when balance might be exceeded, and contrasts with convert_document's refusal behavior, providing clear alternatives.

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

All mdmagic tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Each tool targets a distinct function: credit management, conversion, estimation, template listing/details/recommendation, validation, and settings. Even the three list tools are clearly differentiated by scope (all, built-in, custom). No ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (e.g., check_credit_balance, list_all_templates, validate_markdown). No mixing of styles or vague verbs.

Tool Count5/5

With 10 tools, the surface is well-scoped for a document conversion server. Each tool addresses a necessary step in the conversion workflow without being overengineered or sparse.

Completeness5/5

The tool set covers the full lifecycle: credit checks, cost estimation, markdown validation, template discovery (all/built-in/custom), details, recommendations, conversion, and default settings. No obvious gaps for the intended use case.

Resources

Need Help?