Skip to main content
Glama

Botverse

by cloud.botverse
OverviewDiscussionsAdmin

Convert Inline Content

convert_content

Convert a document inline — pass the content directly as a string (or base64 for binary inputs like .docx). PREFERRED route for documents, and the one to use in sandboxed agent environments (claude.ai, Claude Desktop, Cursor): it runs entirely server-side, so it never needs the direct upload those sandboxes block. Limit: up to 4 MB of content — already huge (a 500-page book is ~1 MB of text). For anything larger, use convert_from_url with a public URL. Supported inputs: md, html, rst, txt (plain text), docx (base64). Supported outputs: docx (Word), pdf, html, txt, md, rst, xlsx. Returns a job_id — poll get_job_status until 'complete', then get_output_content (inline bytes, sandbox-safe) or get_download_url (download link). Flat fee $0.05 per file. TIP: if you have shell access and are NOT sandboxed (e.g. a local coding agent), the botverse CLI (npx botverse convert <file> --to <fmt>) is faster for local files — it streams from disk instead of re-emitting the content through the model.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe file content as a plain text string (for md, html, rst, txt) or base64-encoded bytes (for docx).
encodingNoEncoding of the content field. Defaults to "text". Use "base64" for binary inputs like .docx.
input_formatYesSource format of the content.
output_formatYesTarget format: docx | html | txt | md | rst | pdf | xlsx

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYesUnique identifier for this job. Pass to get_job_status and get_download_url.
statusYesInitial job state — always queued or processing immediately after submission.
estimated_secondsNoRough estimated processing time in seconds. Actual time may vary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses that execution is server-side and sandbox-safe, has a 4 MB content limit, incurs a flat $0.05 per-file fee, returns a job_id requiring polling, and offers inline or download retrieval. No contradictions with readOnlyHint=false or other annotations.

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?

It is front-loaded with purpose and routing, and most sentences carry useful operational detail. It loses a point for restating the supported input/output format enums that the schema already lists, making it longer than strictly necessary.

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 paid asynchronous converter with sandbox restrictions, it covers the full call workflow: input limits, alternative tools, job_id polling, output retrieval methods, and cost. With the output schema also present, nothing needed to invoke it correctly is missing.

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?

Schema coverage is 100%, so the schema already defines content, encoding, and format parameters. The description adds a meaningful invocation constraint not in the schema: up to 4 MB for the content parameter, and confirms base64 for binary inputs like .docx.

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 states a specific verb and resource ('Convert a document inline') and distinguishes this route from siblings such as convert_from_url, convert_file, and the CLI, so an agent can select it without opening other schemas.

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?

It gives explicit when-to-use guidance: preferred for documents and sandboxed agent environments, with a 4 MB limit, and names convert_from_url for larger inputs plus the botverse CLI for non-sandboxed local files. This covers when and when-not to invoke it.

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

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