Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DOCONDA_API_KEYYesYour Doconda API key (e.g., ak_eu_…). Required for the local stdio server; the remote server uses the same key as a Bearer token in the Authorization header.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_documentA

Create a finished document: Word, PDF, PowerPoint, Excel or an artifact (a web page with its own shared database, e.g. a poll or a team checklist). Choose only the format: Doconda works out what kind of document it is (contract, letter, report…) from the request. Give prompt to have it written, or markdown with the content already written. Waits until it is ready and returns download links; after about 4 minutes it returns its id and status instead: call get_document later.

upload_fileA

Upload a file (Word, PDF, PowerPoint, Excel — also the old .doc, .ppt and .xls —, .odt, CSV, TXT, Markdown, HTML, or a PNG, JPEG, GIF or WebP picture; up to 20 MB) to convert or edit it, or to use it as a source. Returns its file_id. Give path for a file on this computer.

convert_fileA

Convert an uploaded file to another format, with no AI. Word, Markdown, text, HTML and .odt → docx, pdf, md, txt, html, odt, rtf; Excel and CSV → xlsx, csv, pdf, md, txt; PowerPoint → pptx, pdf, md, txt; PDF → docx, md, txt; PNG and JPEG → pdf, md. Scanned PDFs and pictures are read with OCR. md, txt, html and csv come back as text (use md to read any file); the rest as a download link valid 5 minutes. The first 1000 conversions each month are free, then 0.01 € each.

edit_documentA

Change an uploaded Word, PowerPoint, Excel or PDF file as asked (e.g. 'blue headings and add a confidentiality clause'). Only what is asked changes; the rest stays identical. Returns the new file (after about 4 minutes, its id and status instead: call get_document later); get_report lists every change, with the text before and after.

list_documentsA

The latest documents made in this project (newest first), with their id and name. Use an id as file_id to convert or edit one, or in source_file_ids to create from it.

get_documentA

A document's status and fresh download links (they expire after 5 minutes). Also to check on a document create_document or edit_document returned before it finished.

get_reportA

What an edit changed (from edit_document): changes lists each passage added, changed or removed, with the text before and after (empty for a created document). For the status and download links use get_document. Until the document finishes it returns report_not_ready; once its retention ends, content_deleted.

read_artifact_dataA

What people have saved in an artifact's page (e.g. poll votes): its collections, or one collection's records, newest first.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 8 tools

Disambiguation5/5

Each tool maps to a distinct action on a distinct object: create, upload, edit, status/download, convert, change report, list, and artifact data read. The closest pair, get_document and get_report, is clearly separated by descriptions (status/links vs. edit diffs). No meaningful misselection risk.

Naming Consistency5/5

All eight tools follow a clean verb_noun snake_case pattern (create_document, upload_file, edit_document, get_document, convert_file, get_report, list_documents, read_artifact_data). The convention is uniform throughout.

Tool Count5/5

Eight tools is well-scoped for a document creation, editing, and conversion service. Each tool covers a necessary lifecycle step without redundancy.

Completeness4/5

Core lifecycle is covered: create, upload, edit, convert, retrieve status/links, inspect changes, and list. Minor gaps remain, notably no delete_document and no way to write/append records to an artifact's collections (only read_artifact_data exists), but agents can mostly work around these.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues