Rapier - Markdown Editor & Art

Convert pictures with Rapier

convert

Use this when the person wants pictures converted to JPEG XL, or JPEG XL pictures converted back. Free, on the person's own device. Opens Rapier's converter in this app's view where the app can show one: pictures from the chat passed in files open there and convert at once, and the person can add more and saves the results. The pictures never reach Rapier's server: the view reads them from the chat on the person's device. Without a view, answers with the converter's link (https://rapier.website/jxl) for the person. files: the chat's pictures; omit it to let the person pick them. quality: lossless, high (default) or medium; effort 1-9 (default 7: higher is smaller and slower). To convert files in your own sandbox, run npx rapier-jxl <file|folder>: it prints each size before and after.

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": "convert"
  }
}

Input Schema

Name	Required	Description
`agent`	No	Your display name on acts; never grants authority.
`files`	No
`effort`	No
`quality`	No
`operation_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds substantial detail beyond annotations: the view opens inside the app, conversion happens on the person's device, pictures never reach Rapier's server, results are saved, and there is a link-only fallback. The only gap is `operation_id`, whose behavior (retries? deduplication?) is never explained, which matters for a non-idempotent (idempotentHint=false) tool.

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?

Front-loads the trigger and the device-local guarantee, then switches to a compact `param: meaning` list. Some clauses are run-on (the view/saves sentence) and the npx tip is ancillary, but nothing is idle filler.

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?

Covers the full workflow (trigger, view path, fallback path, saving, sandbox path) for a mutation-style tool with no output schema. It falls short only on `operation_id` and on what the returned result actually contains when the tool answers with a link instead of a view.

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?

With only 20% schema coverage the description must compensate, and it does for the important parameters: `files` semantics and omission behavior, `quality` values with `high` as default, and `effort` range 1-9 with default 7 and the size/speed tradeoff. `agent` and especially `operation_id` are left unexplained, so it is not complete.

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 concrete verb and resource (convert pictures to/from JPEG XL) and names the specific triggering intent ("Use this when the person wants..."), which separates it cleanly from siblings like open, show, export, or read. No ambiguity about what the tool produces.

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 frames the two directions of use, states that omitting `files` lets the person pick their own pictures, and gives a fallback path when no view is available (returns the converter link). It also names an out-of-band alternative (npx rapier-jxl in the agent's own sandbox) for a different situation.

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

All Rapier - Markdown Editor & Art 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.