Skip to main content
Glama
B-C-Software

Doconda

Official
by B-C-Software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Edit document

edit_document

Change an uploaded Word, PowerPoint, Excel, or PDF file as instructed, altering only what you ask while keeping the rest identical. Returns the new file and a report listing every change.

Instructions

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; get_report lists every change, with the text before and after.

Input Schema

NameRequiredDescriptionDefault
file_idYesFrom upload_file, or the id of a document Doconda made (list_documents).
qualityNoOptional. fast: the cheapest and quickest (about a minute), any style, but it can't copy a file's design. standard: more care, takes minutes. best: the highest quality and price, e.g. to copy a file's design or to edit with comments or tracked changes. auto (default): Doconda picks the level the request needs. The price of the highest level it may use is held from the balance while the document is made and what is not used is returned: with a low balance, pick fast or set max_quality.
max_qualityNoOnly with quality auto: the highest level Doconda may choose. It caps the price and the amount held, e.g. standard.
instructionsYesWhat to change, in the user's words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.5
    • addedInput schema / properties / max_quality
      Added value: +{
+  "description": "Only with quality auto: the highest level Doconda may choose. It caps the price and the amount held, e.g. standard.",
+  "enum": [
+    "fast",
+    "standard",
+    "best"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / quality
      Added value: +{
+  "description": "Optional. fast: the cheapest and quickest (about a minute), any style, but it can't copy a file's design. standard: more care, takes minutes. best: the highest quality and price, e.g. to copy a file's design or to edit with comments or tracked changes. auto (default): Doconda picks the level the request needs. The price of the highest level it may use is held from the balance while the document is made and what is not used is returned: with a low balance, pick fast or set max_quality.",
+  "enum": [
+    "auto",
+    "fast",
+    "standard",
+    "best"
+  ],
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a non-readonly, non-destructive, non-idempotent operation. The description adds useful behavioral context: only requested changes are applied, everything else stays identical, a new file is returned, and get_report can list before/after changes.

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 three compact sentences with the action front-loaded. Every sentence adds either scope, behavioral assurance, or return-value guidance without 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?

There is no output schema, so it is valuable that the description states a new file is returned and points to get_report for the change log. Combined with the rich parameter schema and annotations, it is nearly complete, though explicit sibling routing is still missing.

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%, and the schema already documents file_id, instructions, quality, and max_quality in detail. The description only reinforces that instructions are natural-language requests; it adds no new semantics for the quality controls or parameter constraints.

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 gives a specific verb and resource: change an uploaded Word, PowerPoint, Excel or PDF file. It includes a concrete example and makes clear this edits existing content rather than creating or uploading a new file.

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

Usage Guidelines3/5

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

Usage is implied by 'change an uploaded ... file as asked', but the description does not explicitly say when to choose this over create_document, review_document, or upload_file. The get_report reference explains follow-up inspection, not tool selection.

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

Deploy Server

Other Tools