Skip to main content
Glama

Carbone MCP

by io.carbone

Download Template

download_template
Read-onlyIdempotent

Download the original source file of a stored Carbone template (e.g. the DOCX, XLSX, PPTX, or HTML file that was uploaded). Use this to inspect, edit, or back up a template. Pass a Template ID to download the currently deployed version, or a Version ID to download a specific version. Set sample:true to fetch the JSON sample dataset stored with the template instead of the template file itself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sampleNoIf true, download the JSON SAMPLE DATASET saved with the template (the "sample" array passed to upload_template) instead of the template file. Returns JSON of the form [{ "data": {...}, "complement": {...}, "translations": {...}, "enum": {...} }]. Use it to recover the example data a template expects — handy before calling render_document against an unfamiliar template. Errors if the template was uploaded without a sample.
outputPathNoNOT AVAILABLE on this server, which is reached over HTTP: the template file would be written to the server's disk instead of yours, so passing outputPath is rejected. Use asAttachment to receive the bytes, or returnLink for a one-time download URL.
templateIdYesTemplate ID (64-bit) or Version ID (SHA-256) to download. Template ID — downloads the currently deployed version of the template. Version ID — downloads that exact version regardless of deployment status. Both formats are returned by upload_template and list_templates.
asAttachmentNoIf true, return the template as a downloadable file attachment (base64 resource) instead of inline text/image. Useful in HTTP mode where outputPath is unavailable. Default: false. Ignored when outputPath is set.

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly and idempotent, but the description adds substantial behavioral context: the distinction between Template ID (deployed version) and Version ID, the sample:true behavior, the error if no sample exists, and the note that outputPath is rejected on HTTP servers. These go well beyond the structured fields without contradiction.

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?

The description is four sentences, each serving a distinct purpose: defining the tool, stating use cases, explaining ID semantics, and covering the sample option. It is front-loaded with the most critical information and uses no superfluous words.

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 tool with 4 parameters, complex ID semantics, and HTTP-specific limitations, the description covers all essential aspects: version selection, sample retrieval, and the unavailable outputPath behavior. It even hints at error conditions. No critical gaps are apparent given the tool's complexity and the absence of an output schema.

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 the baseline is set to 3. The main description text adds minimal parameter-level nuance beyond what is already in the schema (e.g., 'sample:true' is mentioned, but the parameter description already explains it fully). The description does not significantly enrich parameter understanding beyond schema definitions.

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 'Download[s] the original source file of a stored Carbone template' with specific examples (DOCX, XLSX, etc.), which precisely conveys the verb and resource. It differentiates from siblings like render_document by emphasizing 'source file,' making the purpose unambiguous.

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?

It provides clear usage scenarios ('Use this to inspect, edit, or back up a template') and references the alternative workflow 'before calling render_document against an unfamiliar template.' However, it does not explicitly state when NOT to use the tool or name an alternative like render_document for generated output, which would strengthen the guidance.

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

All Carbone MCP 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 resource or action: document conversion, template lifecycle, metadata, status checks, and listing operations are all clearly separated. The potential overlap between convert_document and render_document is explicitly addressed in their descriptions, with clear guidance on when to use each.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: convert_document, delete_template, download_template, get_api_status, list_templates, render_document, upload_template, etc. Verbs are precise and match the operation performed, making the API predictable.

Tool Count5/5

Eleven tools is well-scoped for a document templating and rendering server. Each tool covers a meaningful part of the workflow: template management, rendering, conversion, metadata, and account-level discovery, without redundancy or bloat.

Completeness5/5

The tool surface covers the full template lifecycle: upload, list, download, update metadata, delete, and render. It also includes conversion, status checking, capability discovery, and tag/category enumeration, leaving no obvious dead ends for typical Carbone workflows.

Resources