Skip to main content
Glama

mdmagic

by ai.mdmagic.api

check_credit_balance

Read-onlyIdempotent

Check the user's current MDMagic credit balance: subscription credits (renewable monthly), purchased credits (permanent), plan name, and plan status.

CALL THIS PROACTIVELY when:

  • The user asks 'how many credits do I have' or similar

  • After a conversion, if the user wants to know what's left (also returned by convert_document directly)

  • Before a conversion of an unusually large document, to warn the user if balance is borderline

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly=true, idempotent, not destructive. Description adds detail about returned fields (subscription vs purchased credits) and proactive call scenarios. No contradictions.

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?

Description is well-structured with purpose first, then usage guidance. Each sentence adds value. Could be slightly more concise, but it's efficient for the given detail.

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 tool with comprehensive annotations, the description is complete. It includes return contents, proactive call scenarios, and links to sibling behavior.

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?

No parameters exist, so baseline 4. Description does not need to add parameter info.

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 checks MDMagic credit balance and lists the components (subscription credits, purchased credits, plan name, status). It is distinct from sibling tools like convert_document and estimate_conversion_cost.

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

Usage Guidelines4/5

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

Explicitly specifies when to call (user asks about credits, after conversion, before large conversion) and acknowledges that convert_document also returns balance. Slight room for improvement on when not to call.

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

All mdmagic toolsInspect
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