slim-down

convert

Converteert tekst of gestructureerde data (JSON, YAML, CSV, HTML, Markdown, platte tekst) naar Markdown of een ander doelformaat, met dezelfde logische conversiematrix als de doc2mk REST API.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>"
    },
    "name": "convert"
  }
}

Input Schema

Name	Required	Description
`input`	Yes	De ruwe tekst of data om te converteren
`pretty_json`	No	Of JSON-output leesbaar geformatteerd moet worden
`source_format`	No	Bronformaat (bv. json, yaml, csv, html, markdown); standaard auto-detectie
`target_format`	No	Doelformaat (bv. markdown, html, json, yaml, csv, docx, excel); standaard markdown

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0

Behavior2/5

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

No annotations exist, so the description carries the full burden, and it only states that conversion happens. It does not say what is returned (a converted string? a document?), how unsupported or mismatched source/target combinations fail, or how auto-detection behaves — despite claiming parity with an external REST API the agent has no visibility into.

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 well-formed sentence that front-loads the verb, resource, and format coverage with no redundancy. The trailing 'doc2mk REST API' clause is the only element that adds little for an agent that cannot consult that API.

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 four-parameter transformation tool with no annotations and no output schema, the definition covers what goes in and the default output format but says nothing about the returned value or failure modes. It is adequate to attempt a call, but thin for understanding the result.

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 all four parameters (input, source_format, target_format, pretty_json) are already documented in the schema, which sets the baseline at 3. The description corroborates the format list and the Markdown default but adds no syntax, casing, or accepted-value detail beyond the schema, and there are no enums to clarify.

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?

States a specific verb (converteert) and resource (tekst of gestructureerde data), and enumerates the source formats plus the default target (Markdown). The framing around raw text/data implicitly separates it from the file-based sibling convert_file, but it never names or contrasts with that sibling, leaving a small ambiguity about which to pick.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and the sibling convert_file is never mentioned, so an agent must infer that this tool takes inline content rather than a file path. The reference to the 'doc2mk REST API conversion matrix' is background context, not actionable routing guidance.

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

All slim-down tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?